Continuous delivery

As explained in Google Anthos in Action

A continuous delivery pipeline is an automated sequence of steps that builds, tests, and deploys software while keeping changes releasable.

Continuous delivery keeps changes of all types—features, configuration, fixes, experiments, infrastructure, applications, databases, and static resources—releasable for safe, rapid, sustainable production delivery. A pipeline automates the path from source to production, improving reliability, predictability, visibility, and risk control. section 12.1

A practical continuous-delivery approach emphasizes:

• Following continuous integration: frequent check-ins trigger automated builds and tests before delivery. section 12.1
• Keeping integration manageable through trunk-based development; long-lived branches create conflicts and manual work that can stall CI. section 12.1.5
• Distinguishing delivery from deployment: continuous deployment adds automatic promotion to user environments without manual intervention. section 12.2

Cloud Run deployment pipeline

A Google Cloud implementation can monitor Cloud Source Repositories, use Cloud Build to trigger deployment after a code merge, and let Cloud Run manage configured blue/green, canary, or rolling traffic shaping. Repository setup includes gcloud initialization, repository creation, authentication, and ordinary Git operations. section 12.4.1

Figure 12.26 Cloud Source Repositories integrations

Use the integration diagram to trace how repositories, build automation, event triggers, and Cloud Run deployment fit together. section 12.4.1

How Google Anthos in Action covers it

How deep it goes

Defines delivery, contrasts deployment, and demonstrates a Cloud Run integration without detailing complete pipeline implementation.

Examples

Uses frequent integration, long-lived branch conflicts, and a Cloud Source Repositories–Cloud Build–Cloud Run deployment pipeline as examples.

What it assumes

Assumes continuous integration, Git usage, repository authentication, and basic familiarity with cloud deployment services.

What you can do after

Apply it via Cloud Source Repositories and Cloud Build to automate Cloud Run deployments and improve delivery reliability and visibility.

How it connects

Connects continuous integration, continuous deployment, trunk-based development, DevOps, site reliability engineering, and infrastructure as code.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Related concepts

• continuous deploymentincludes · Continuous deployment is a software delivery practice in which validated changes are automatically released to a target environment, typically production, without manual approval.
• continuous integrationkind of · Continuous integration is a software development practice in which code changes are integrated frequently into a shared codebase and automatically validated.
• DevOpsused by · DevOps is a set of organizational, cultural, and technical practices that integrates software development and IT operations through collaboration, automation, and feedback.
• testhas part · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.