Continuous delivery

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Continuous Delivery (CD) is a software engineering approach in which teams keep producing valuable software in short cycles and ensure that the software can be reliably released at any time.[1] It is used in software development to automate and improve the process of software delivery. Techniques such as automated testing and continuous integration (CI) allow software to be developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead. CD builds on CI by adding the regular deployments to production as part of the process, however CD is not a requirement of CI. The technique (CD) was one of the assumptions of extreme programming but at an enterprise level has developed into a discipline of its own, with job descriptions for roles such as "buildmaster" calling for CD skills as mandatory.


Continuous Delivery process diagram.png

Continuous delivery treats the commonplace notion of a deployment pipeline[2] as a lean Poka-Yoke:[3] a set of validations through which a piece of software must pass on its way to release. Code is compiled if necessary and then packaged by a build server every time a change is committed to a source control repository, then tested by a number of different techniques (possibly including manual testing) before it can be marked as releasable.

Developers used to a long cycle time may need to change their mindset when working in a CD environment. It is important to understand that any code commit may be released to customers at any point. Patterns such as feature toggles can be very useful for committing code early which is not yet ready for use by end users. Using NoSQL can eliminate the step of data migrations and schema changes, often manual steps or exceptions to a continuous delivery workflow.[4] Other useful techniques for developing code in isolation such as code branching are not obsolete in a CD world, but must be adapted to fit the principles of CD - for example, running multiple long-lived code branches can prove impractical, as a releasable artifact must be built early in the CD process from a single code branch if it is to pass through all phases of the pipeline.

Implementation and usage[edit]

Continuous Delivery has been implemented in many different places, e.g.,[5],[citation needed] Facebook,[citation needed] Google,[6] Paddy Power [1] and Wells Fargo.[7]


Several benefits of Continuous Delivery have been reported.[1]

  • Accelerated Time to Market: CD lets an organization deliver the business value inherent in new software releases to customers more quickly. This capability helps the company stay a step ahead of the competition, in today’s competitive economic environment.
  • Building the Right Product: Frequent releases let the application development teams obtain user feedback more quickly. This lets them work on only the useful features. If they find that a feature isn’t useful, they spend no further effort on it. This helps them build the right product.
  • Improved Productivity and Efficiency: Significant time savings for developers, testers, operations engineers, etc. through automation.
  • Reliable Releases: The risks associated with a release have significantly decreased, and the release process has become more reliable. With CD, the deployment process and scripts are tested repeatedly before deployment to production. So, most errors in the deployment process and scripts have already been discovered. With more frequent releases, the number of code changes in each release decreases. This makes finding and fixing any problems that do occur easier, reducing the time in which they have an impact.
  • Improved Product Quality: The number of open bugs and production incidents has decreased significantly.
  • Improved Customer Satisfaction: A higher level of customer satisfaction is achieved.

See also[edit]

Further reading[edit]

  • Humble, Jez; Farley, David (2010). Continuous Delivery: Reliable Software Releases Through Build, Test and Deployment Automation. Addison-Wesley. ISBN 978-0-321-60191-9. 


  1. ^ a b c Chen, Lianping (2015). "Continuous Delivery: Huge Benefits, but Challenges Too". IEEE Software 32 (2): 50. doi:10.1109/MS.2015.27. 
  2. ^ Jez Humble, Chris Read, Dan North (2006). "The Deployment Production Line". IEEE Computer Society. Proceedings of Agile 2006. 
  3. ^ Fitzgerald, Brian (2014-06-03). Continuous Software Engineering and Beyond: Trends and Challenges (PDF). 1st International Workshop on Rapid Continuous Software Engineering. New York, NY: Association for Computing Machinery. pp. 1–9. doi:10.1145/2593812.2593813. ISBN 978-1-4503-2856-2. Retrieved 2014-10-24. 
  4. ^ Kluge, Lars (12 September 2013). "Continuous Deployment with MongoDB at Kitchensurfing". Retrieved 3 January 2014. 
  5. ^ "Implementing Continuous Delivery at Yahoo!". 23 October 2013. 
  6. ^ Humble, Jez (13 February 2014). "The Case for Continuous Delivery". Retrieved 16 July 2014. 
  7. ^ jFrog (December 2014). "2014-year-continuous-integration-revolution". 

External links[edit]