You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline. You need to resolve the issue following Site Reliability Engineering practices. What should you do?

Question

Accepted Answer

D. Run a Git compare between the previous and current Cloud Build Configuration files to find and SRE principles emphasize using version control systems like Git to manage all configurations. By running a Git compare between the last known good configuration and the current non-working configuration, you can quickly pinpoint the exact change that caused the pipeline to fail, facilitating a rapid fix or rollback.

Answer

A. Disable the CI pipeline and revert to manually building and pushing the artifacts. Disabling the CI pipeline and reverting to manual processes goes against automation principles and is not a resolution, but a workaround that reduces reliability and efficiency.

Answer

B. Change the CI pipeline to push the artifacts is Container Registry instead of Docker Hub. Changing the artifact destination is irrelevant to a pipeline not building artifacts due to a configuration error and does not address the root cause of the build failure.

Answer

C. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix Uploading the YAML to Cloud Storage and using Error Reporting might help with general logging but doesn't specifically target comparing versions of a configuration file to pinpoint a recent change as effectively as Git.

You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration…

Question

Options

How the community answered

Why each option

Topics

Community Discussion