Continuous Delivery vs Continuous Deployment
Continuous delivery and continuous deployment both test and build every change on their own, but only one ships it by itself. With delivery, the code is always ready. A person clicks to go live. With deployment, there is no click. Each change that passes the tests goes straight to users.
Continuous Delivery
Keeping code ready to release at all times. Going live is one click.
Continuous delivery means your code is always ready to release, at the push of a button. Every change that passes the tests is built and sent to staging on its own. Going live is one click, but a person still decides when. Releases become small and boring, not big and scary. It is the step after CI.
Continuous Deployment
Each change that passes the tests goes live on its own. No button.
Continuous deployment means each change that passes the tests goes live on its own. A developer merges code, and minutes later users have it. It needs very good tests, because nothing else stands in the way. Teams pair it with feature flags and quick rollbacks. Some teams ship dozens of times a day this way.
In one line
- Continuous Delivery
- Keeping code ready to release at all times. Going live is one click.
- Continuous Deployment
- Each change that passes the tests goes live on its own. No button.