an IT practice made popular by a book of the same name in which software is automatically evaluated for quality and deployed into environments all the way up to production.
— DevOps for the Modern Enterprise, Mirco Hering
4 of our books and 4 talks define this term — and their definitions are worth reading side by side.
an IT practice made popular by a book of the same name in which software is automatically evaluated for quality and deployed into environments all the way up to production.
— DevOps for the Modern Enterprise, Mirco Hering
what Jez Humble would later term continuous delivery (he later authored a book by the same name), describing it as a way for software development and operations to work as a seamless, transparent, integrated team.
— Deming's Journey to Profound Knowledge, in “Chapter 16: The Digital Cambrian Explosion”, John Willis with Derek Lewis
a set of technical practices known as continuous delivery . Continuous delivery includes creating the foundations of our automated deployment pipeline, ensuring that we have automated tests that constantly validate that we are in a deployable state, having developers integrate their code in to trunk daily, and architecting our environments and code to enable low-risk releases
— The DevOps Handbook, in “Part III Introduction”, Gene Kim, Jez Humble, Patrick Debois, John Willis, and Nicole Forsgren
continuous delivery, or the ability to deliver a continuous stream of small increments of software capability
— Signals and Levers, in the text
Continuous delivery is not just a technical problem. It's an organizational change that starts with your stakeholders and goes all the way down to your development and closes that gap, closes that loop
— Brent Pendergraft, Bryan Finster · Continuous Delivery: Solving the Talent Problem, San Francisco 2017 · at 21:35
We define continuous delivery in our model as being comprised of all of these things: effective test data management; comprehensive, fast, and reliable test and deployment automation; trunk-based development, which means everyone is working on branches that get checked into trunk or master on at least a daily basis.
— Dr. Nicole Forsgren, Jez Humble · What We Learned from the 2016 State of DevOps Report, San Francisco 2016 · at 17:26
I can ship the head of my master branch at any time
— Steve Neely · There is no Weekend Release, Only Zuul: Continuous Delivery for a 10-Year-Old Codebase, San Francisco 2014 · at 3:58
CD means we can deliver on command, on demand
— Bryan Finster · Minimum Viable Continuous Delivery, Virtual US 2022 · at 4:08
See also continuous delivery pipeline · trunk-based development · DevOps · integration testing · product-oriented management · abstract environment configuration
Filed under DevOps & Delivery
Every book and audiobook, the video library, the courses, and the MCP. The papers stay free.