Summary
Continuous Delivery is a practice in which software is kept in a continuously releasable state through automated build, test, and staging pipelines, with the final push to production remaining a deliberate business decision.
What is Continuous Delivery?
Continuous Delivery (CD) builds on Continuous Integration by extending the automation beyond the build and test phase. Every change that passes the automated test suite is automatically deployed to a staging environment that mirrors production. The software is therefore always in a state where it could be released at any moment with a single button press or approval.
The key distinction from Continuous Deployment is that the release to production is still a manual, intentional step. This allows product teams and release managers to coordinate timing, regulatory requirements, or marketing activities around a release without slowing down the engineering pipeline.
Achieving Continuous Delivery requires a comprehensive automated test suite, environment parity between staging and production, and feature flags to decouple deployment from release.
Why is Continuous Delivery relevant?
- Reduced release risk: Smaller, more frequent releases are less risky and easier to troubleshoot
- Business agility: Teams can release on demand when business conditions are right, not when the pipeline allows
- Feedback loop: Rapid deployment to staging surfaces integration and configuration issues early