You have written unit tests for a Kubeflow Pipeline that require custom libraries. You want to automate the execution of unit tests with each new push to your development branch in Cloud Source Repositories. What should you do?
You have written unit tests for a Kubeflow Pipeline that require custom libraries. You want to automate the execution of unit tests with each new push to your development branch in Cloud Source Repositories. What should you do?
Using Cloud Build, set an automated trigger to execute the unit tests when changes are pushed to your development branch. Cloud Build is specifically designed for continuous integration and delivery (CI/CD) on Google Cloud Platform, making it the most appropriate and efficient choice for automating the execution of unit tests with each new push to your development branch. It integrates smoothly with Cloud Source Repositories and supports running custom tasks like unit tests without the need for additional complexities.
B. GCP recommends to use Cloud Build when building KubeFlow Pipelines. It's possible to run unit tests in Cloud Build. And, the others seems overly complex/unnecessary
B makes sense because of this: https://cloud.google.com/architecture/architecture-for-mlops-using-tfx-kubeflow-pipelines-and-cloud-build#cicd_architecture
The image explains a lot
Easy one, B, Cloud Build is the tool for CI/CD.
B it is.
B is the only sensible answer as its a feature of CloudBuild everything else is the delusions of a madmen
Correct answer is "B"
B is the Google-recommended best practice.
ans: B
Because it is the most automatic of the options
Went with B
Cloud Build is the best choice but the other answers are feasible.
A, C, D need addiontal maunal tasks. B is correct.
B. Cloud Build.
B: No need of any Pub/Sub stuff