What is Continuous Delivery? Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands …

A key goal of continuous delivery is to change the economics of the software delivery process to make it economically viable to work in small batches so we can obtain the many benefits of this approach.

Despite these barriers, helping software development teams implement continuous integration should be the number one priority for any organization wanting to start the journey to continuous delivery.

The key pattern introduced in continuous delivery is the deployment pipeline. This pattern emerged from several ThoughtWorks projects where we were struggling with complex, fragile, painful manual …

In this talk, Jez will present the architectural principles and patterns that enable continuous delivery at internet scale, and discuss how to incrementally evolve existing systems in order to deploy them.

Continuous delivery rests on three foundations: comprehensive configuration management, continuous integration, and continuous testing. In this section, you can read an overview of each of these …

Jez Humble is co-author of several books on software including Shingo Publication Award winner Accelerate and Jolt Award winner Continuous Delivery. He has spent his career tinkering with code, …

Aug 13, 2010 · Implementing continuous delivery means making sure your software is always production ready throughout its entire lifecycle - that any build could potentially be released to users at the touch …

In continuous delivery, we introduce two new architectural attributes: testability and deployability. In a testable architecture, we design our software such that most defects can (in principle, at least) be …

Our goal should be to be able to use our normal release process for emergency fixes—which is precisely what continuous delivery enables, on the basis of comprehensive configuration management.