Comparison
Continuous deliveryvsContinuous integration
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 integration
your change was merged and verified against everyone else's within the hour, not at the end of the sprint.
The practice of integrating everyone's work into a shared mainline frequently, with automated verification each time. The important half is the practice, not the server: a team with a build pipeline and week-long branches is not doing continuous integration, whatever the tool is called. The value is that integration problems are found while they are small and while the person who caused them still remembers the change.
Full entry →