Continuous integration
Continuous integration is a software development practice of frequently integrating changes into a shared codebase and automatically validating them with builds, tests, or other checks.
Vibe Engineering
Continuous integration is the practice of frequently merging changes into a shared codebase and automatically building and testing them.
- How it is used
- Supports fast, reliable feedback and automated AI work on shared code changes.
- How deep it goes
- Details review routing, batching, caching, and pipeline timing, while leaving basic pipeline construction unspecified.
- Examples
- Compares a two-pass review pipeline with an all-deep-review baseline and reports daily file volumes and monthly costs.
- What you can do after
- Operate/configure a CI workflow by timing feedback and choosing review routing, batching, and caching for automated tasks.
Shipping Go: Develop, deliver, discuss, design, and go again
Continuous integration is a software development practice in which code changes are frequently merged into a shared codebase and automatically built and verified.
- How it is used
- Supports small, shareable increments by turning code check-ins into automated build feedback.
- How deep it goes
- Works through repository organization and an initial pipeline result, but does not specify pipeline configuration in the supplied evidence.
- Examples
- Uses a Go hello API, README milestones, a Git push, and a downloadable pipeline-built binary.
- What you can do after
- Build it from scratch as a minimal repository-to-artifact workflow, then inspect pipeline feedback and iterate.
Test Driven: Practical TDD and Acceptance TDD for Java Developers
A software development practice of integrating changes into a shared source repository frequently and verifying the integrated code, typically with automated tests.
- How it is used
- Supports test-driven development by integrating frequent small changes and checking that the combined code still works.
- How deep it goes
- Explains the integration workflow and the speed-versus-confidence trade-off, without detailing server configuration.
- Examples
- Uses a developer’s local test subset, repository commit, server build, and emailed report to illustrate the workflow.
- What you can do after
- Evaluate a continuous integration workflow by distinguishing frequent integration from server automation and weighing the risks of a partial local test run.
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.
- How it is used
- Uses frequent integration and automated validation to support a reliable, repeatable software delivery workflow.
- 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 you can do after
- Apply CI by integrating changes frequently and validating them through automated builds and tests.
Read how Google Anthos in Action explains continuous integration →
BDD in Action, Second Edition
Continuous integration is a development practice in which changes are integrated into a shared codebase frequently and validated automatically.
- How it is used
- Automates build-and-test feedback after each repository change to expose integration issues and regressions early.
- How deep it goes
- Defines the commit-triggered build-and-test loop and stresses comprehensive automation, but stops short of implementation details.
- Examples
- Uses collaborative automated scenarios, release testing, regression checks, and progress dashboards based on test results.
- What you can do after
- Operate a commit-triggered build-and-test process that supports faster, more reliable releases and earlier regression detection.
Read how BDD in Action, Second Edition explains continuous integration →
The Cloud at Your Service: The when, how, and why of enterprise cloud computing
A software development practice in which code changes are integrated frequently and automatically checked through builds and tests.
- How it is used
- Uses automated builds and tests to provide frequent software-quality feedback and support broader testing and faster release decisions.
- How deep it goes
- Explains automated build-and-test feedback and remote-agent scaling, then connects CI to functional testing and continuous deployment.
- Examples
- Uses a project with over 40 builds, 30-second-to-15-minute build times, queued work, and Hudson and Bamboo as CI package examples.
- What you can do after
- Operate CI by running automated build and test scripts remotely and adding build agents when tasks queue for resources.
Kargo in Action
Continuous integration is the practice of automatically building and testing changes and publishing the resulting artifacts.
- How it is used
- Builds and tests artifacts, then publishes them to a repository as the first layer of the delivery stack.
- How deep it goes
- Defines CI’s artifact-publishing boundary and distinguishes its role from promotion and cluster reconciliation.
- Examples
- Names GitHub Actions, GitLab CI, and Jenkins as CI systems.
- What you can do after
- Evaluate CI’s boundary by identifying artifact publication as its endpoint, before promotion or cluster reconciliation.
Also covered in
- Spring Start Here, Second EditionIn early access (MEAP)
- Build High Value Software SystemsIn early access (MEAP)
- gRPC Microservices in Go
What to know first
- software testingSoftware testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
- integration testAn integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
- automationAutomation is the execution of tasks or processes by machines or software with reduced direct human intervention.
- code reviewCode review is the systematic examination of source code or proposed changes to assess correctness, quality, risks, or conformance to requirements or standards.
Related concepts
- software testinguses · Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
- 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.
- repositoryuses · A software repository is a managed collection of a project's files and artifacts, often preserving their version history.
- architectural testinguses · Architectural testing automatically checks whether a codebase conforms to specified structural and dependency rules.
- automated testinguses · Automated testing is the execution and evaluation of software tests by programs or tools rather than by manually performing each test procedure.
Questions about continuous integration
What is continuous integration?
Continuous integration is a software development practice of frequently integrating changes into a shared codebase and automatically validating them with builds, tests, or other checks.
Which Manning books explain continuous integration?
Vibe Engineering, Shipping Go: Develop, deliver, discuss, design, and go again, Test Driven: Practical TDD and Acceptance TDD for Java Developers, Google Anthos in Action, BDD in Action, Second Edition, The Cloud at Your Service: The when, how, and why of enterprise cloud computing and Kargo in Action.
What should I know before learning continuous integration?
Manning books that teach continuous integration usually introduce software testing, integration test, automation and code review first.
What is continuous integration a kind of?
Continuous integration is a kind of value stream. 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.
What is continuous integration also called?
Continuous integration is also called CI.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.






