Continuous Delivery vs Continuous Deployment

Jez Humble posted a blog entry with the same title in 2010, but if you haven’t read the entry, or just want a quick explanation, here’s the short version:

A continuous delivery pipeline automatically tests the application, but keeps the deployment decision as a manual step. A continuous deployment pipeline, on the other hand, will automatically deploy this working version. There is no “right” way. Different organizations have different needs. Use the one that delivers the most value to your customers!

Get in touch via my homepage if you have questions or comments!

16 responses on “Continuous Delivery vs Continuous Deployment

  1. Good summery! A rule of thumb in CD is that every commit should be a release candidate but the release should be a political decision and done manually.

    If anyone has more interest in CD there will be a full day continuous delivery seminar in Stockholm on Dec. 5th. The seminar will be held at the Royal Danish Embassy and done by Praqma, Danish Continuous Delivery experts and will give a comprehensive introduction to the vocabulary and concepts of continuous delivery and show how continuous delivery can bring value to businesses.
    Check for more information.

  2. Diagram says it all, very useful in understanding very subtle difference between the two.

Comments are closed.