Continuous Integration
Integrate work to trunk at least daily with automated testing to maintain a releasable codebase.
CD Practices
Concise definitions of the core continuous delivery practices from MinimumCD.
less than a minute
These pages define the minimum practices required for continuous delivery. Each page covers what the practice is, why it matters, and what the minimum criteria are. For migration guidance and tactical how-to content, follow the links to the corresponding phase pages.
Core Practices
- Continuous Integration - Integrate work to trunk at least daily with automated testing
- Trunk-Based Development - All changes integrate into a single shared trunk
- Single Path to Production - One automated pipeline for all changes to reach any environment
- Deterministic Pipeline - Same inputs always produce the same outputs
- Definition of Deployable - Automated criteria that determine production readiness
- Immutable Artifacts - Build once, deploy everywhere without modification
- Production-Like Environments - Test in environments that mirror production
- Rollback - Fast, automated recovery from any deployment
- Application Configuration - Separate what varies between environments from what does not
Trunk-Based Development
All changes integrate into a single shared trunk with no intermediate branches.
Single Path to Production
All deployments flow through one automated pipeline - no exceptions.
Deterministic Pipeline
The same inputs to the pipeline always produce the same outputs.
Definition of Deployable
Automated criteria that determine when a change is ready for production.
Immutable Artifacts
Build once, deploy everywhere. The artifact is never modified after creation.
Production-Like Environments
Test in environments that mirror production to catch environment-specific issues early.
Rollback
Fast, automated recovery from any deployment.
Application Configuration
Separate what varies between environments from what does not.