Delivery for Google Clouds
Delivery on Google Cloud is the automation that moves code from a repository to a running service. Cloud Build runs build and test steps from a configuration file, Artifact Registry stores the resulting images, and triggers deploy to Cloud Run or GKE. Automation makes releases repeatable and removes manual steps that cause mistakes.
Stage: Operations · Part of the Google Cloud roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Write a cloudbuild.yaml that builds and pushes a container image
- Create a build trigger that runs on each push to a branch
- Store images in Artifact Registry and tag them by commit
- Deploy a new Cloud Run revision automatically after a successful build
- Roll back by routing traffic to a previous revision
Delivery interview questions
What does a Cloud Build trigger do?
A trigger starts a build automatically when an event occurs, such as a push to a branch or a tag in a connected repository. It reads the build steps from cloudbuild.yaml or a Dockerfile, so every change is built and tested the same way.
How can you roll back a bad release on Cloud Run?
Each deployment creates a revision. You can shift traffic back to an earlier revision from the console or with gcloud run services update-traffic, which restores the previous behaviour immediately without rebuilding the image.
Where Delivery fits in the Google Cloud roadmap
Delivery belongs to the Operations stage (advanced level). Keep it running.
Other units in this stage
Back to the full Google Cloud roadmap