Continuous integration
Continuous integration is a software development practice in which code changes are integrated frequently into a shared codebase and automatically validated.
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.
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 →
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.
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.