CI vs Continuous Delivery vs Continuous Deployment
You'll learn: How to distinguish three related but distinct levels of automation in modern software delivery pipelines.
These three practices build on each other like steps on a ladder, each adding more automation:
Continuous Integration (CI)
What it automates: Integration and validation.
Every code change is automatically merged into the main branch, built, and tested. The output is a verified, tested artifact ready for further steps. CI answers: "Is this code safe to integrate?"
Analogy: A factory quality control station that checks every widget coming off the line, but doesn't ship them yet.
Continuous Delivery (CD)
What it automates: Release readiness.
Extends CI by ensuring every change that passes tests is automatically prepared for release — packaged, versioned, and deployable to production at any time. But the actual deployment requires a manual approval or button push. CD answers: "Is this code ready to ship?"
Analogy: Your packages are boxed, labeled, and sitting at the loading dock. You still decide when the truck leaves.
Continuous Deployment
What it automates: Production deployment.
The final step: every change that passes all automated checks is automatically deployed to production without human intervention. There's no manual gate. Continuous Deployment answers: "Is this code automatically shipped?"
Analogy: The truck leaves automatically the moment packages pass inspection — no waiting, no approval needed.
The Key Difference
- CI: Automated integration + testing
- Continuous Delivery: CI + automated release preparation + manual production deployment
- Continuous Deployment: CI + automated release preparation + automatic production deployment
Key Takeaway: CI validates changes, Continuous Delivery keeps you release-ready at all times (manual deploy), and Continuous Deployment removes the final manual step by auto-deploying to production.