Question

Your team maintains a microservice that is built by a Cloud Build trigger on every merge to the main branch. Currently, an engineer manually runs 'gcloud deploy releases create' after each successful build to push the image through the dev, staging, and prod delivery pipeline. Leadership wants every successful main-branch build to automatically create a new Cloud Deploy release and begin rollout to the dev target, while preserving the existing manual approval gate before staging. What is the most appropriate way to connect the build to the delivery pipeline?

Accepted Answer

Add a final build step in the Cloud Build configuration that runs 'gcloud deploy releases create' referencing the delivery pipeline and the newly built image, using the build's short SHA as the release name.

Answer

Configure a Cloud Deploy trigger to poll Artifact Registry every five minutes and automatically create a release whenever a new image tag appears.

Answer

Enable automatic promotion on the delivery pipeline's dev stage so that Cloud Deploy detects pushed images and starts a rollout without any release creation step.

Answer

Replace the Cloud Build trigger with a Cloud Deploy trigger on the source repository so that Cloud Deploy builds the image and creates the release in a single operation.