Continuous integration

As explained in Google Anthos in Action

Continuous integration is a software development practice in which code changes are frequently integrated into a shared codebase and validated by automated builds and tests.

Continuous integration (CI) is a software development practice in which developers check in code frequently—at least daily—and automatically build and test each integrated change. It creates reliable, repeatable builds and a fast feedback loop. section 12.1

A CI workflow typically combines:

• A Git source repository for storing and versioning application code. section 12.4
• A CI server that automates validation, builds, and tests after integration. section 12.1 section 12.4
• A container registry for storing built container images. section 12.4
• Code reviews, testing, and container-image builds before deployment continues. section 12.0

Anthos application workflow

A developer changes a Python or Go Hello World application, previews it during continuous development, commits it to Git, and triggers CI for code review, testing, and container-image builds. Operators then configure Kubernetes deployments for development, test, and production environments. section 12.0

Figure 12.1 The CI/CD workflow

Use the CI/CD workflow diagram to trace how development, integration, and deployment activities connect. section 12.0

How Google Anthos in Action covers it

How deep it goes

Defines the practice and identifies repositories, registries, and CI servers, but defers detailed tool configuration.

Examples

Uses an Anthos Hello World application implemented in Python or Go and integrated through Git, testing, and container-image builds.

What it assumes

Assumes application development and Git usage while introducing the CI/CD workflow and its core components.

What you can do after

Apply CI by integrating changes frequently and validating them through automated builds and tests.

How it connects

Connects continuous integration with Git, code review, automated testing, container images, Kubernetes, and continuous delivery.

liveBookmanning.com

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

Also explained in

• 

  liveBookmanning.com
  Shipping Go: Develop, deliver, discuss, design, and go againContinuous integration is a software development practice in which code changes are frequently merged into a shared codebase and automatically built and verified.
• 

  liveBookmanning.com
  BDD in Action, Second EditionContinuous integration is a development practice in which changes are integrated into a shared codebase frequently and validated automatically.

Compare how 3 books explain continuous integration →

Related concepts

• testuses · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
• value streamkind of · A value stream is the complete sequence of activities, decisions, handoffs, and information flows through which work creates and delivers value to a customer or user.
• automationuses · Automation is the execution of tasks or processes by machines or software with reduced direct human intervention.
• GitHub Actionsused by · GitHub Actions is GitHub’s workflow automation platform for defining and running jobs in response to repository events, schedules, and other triggers.
• continuous deliveryincludes · Continuous delivery is a software practice that automates building and validating changes to keep them in a releasable state, ready for deployment.

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.