A cloud architecture team is setting up an automated Continuous Delivery pipeline for a web service on Google Cloud using Cloud Build, Artifact Registry, and Cloud Deploy. What is the correct chronological sequence of steps to safely build, validate, and roll out a new software release to production?
- 1Build the container image using Cloud Build and store it in Artifact Registry with vulnerability scanning enabled.
- 2Create a Cloud Deploy release specifying the container image digest and target delivery pipeline definition.
- 3Deploy the release to the staging target environment and execute automated integration tests.
- 4Promote the release to the production target environment to initiate progressive canary traffic shifting.
Cevap
The correct sequence starts with building and scanning the container image in Artifact Registry, followed by creating a Cloud Deploy release, deploying to a staging target for automated validation, and finally promoting the release to the production target for progressive canary rollout.
A standard automated deployment pipeline enforces strict stage dependencies: source code is first compiled into a container image and scanned for vulnerabilities in Artifact Registry; next, a Cloud Deploy release is initialized referencing this immutable artifact; the release is then deployed to staging for automated integration testing; finally, upon successful test completion, the release is promoted to production.
Adım Adım Çözüm
Anahtar Kavram
Automated Deployment Pipeline Order and Progression Gates