Comparison
Continuous deliveryvsContinuous deployment
Continuous delivery
every commit on main was releasable, and shipping was a decision rather than a project.
Keeping the software in an always-releasable state so that releasing is a business decision rather than an engineering effort. It is distinct from deploying every commit: the point is that you could, at any moment, within minutes. It changes what risk means, because small frequent releases fail smaller and are diagnosed faster than the quarterly one everyone dreads.
Full entry →Continuous deployment
the merge went to production on its own and nobody pressed anything.
Every change that passes the pipeline goes to production automatically, with no human gate. It is a step beyond continuous delivery and it requires more than confidence in the tests: progressive rollout, real monitoring and a fast automatic rollback, because the safety net is no longer a person. It is not correct everywhere, and the honest reason to skip it is usually regulatory or contractual rather than technical.
Full entry →