Continuous Delivery: Reliable Software Releases through B... and over 2 million other books are available for Amazon Kindle . Learn more
  • RRP: £35.99
  • You Save: £7.20 (20%)
FREE Delivery in the UK.
In stock.
Dispatched from and sold by Amazon.
Gift-wrap available.
Continuous Delivery: Reli... has been added to your Basket
Trade in your item
Get a £10.50
Gift Card.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation (Addison-Wesley Signature) Hardcover – 27 Jul 2010

See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
£25.95 £20.82

Frequently Bought Together

Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation (Addison-Wesley Signature) + Continuous Integration: Improving Software Quality and Reducing Risk (Martin Fowler Signature Books) + Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley Signature)
Price For All Three: £100.92

Buy the selected items together

Trade In this Item for up to £10.50
Trade in Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation (Addison-Wesley Signature) for an Amazon Gift Card of up to £10.50, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Product details

More About the Authors

Discover books, learn about writers, and more.

Product Description


“If you need to deploy software more frequently, this book is for you. Applying it will help you reduce risk, eliminate tedious work, and increase confidence. I’ll be using the principles and practices here on all my current projects.”

Kent Beck, Three Rivers Institute


“Whether or not your software development team already understands that continuous integration is every bit as necessary as source code control, this is required reading. This book is unique in tying the whole development and delivery process together, providing a philosophy and principles, not just techniques and tools. The authors make topics from test automation to automated deployment accessible to a wide audience. Everyone on a development team, including programmers, testers,  system administrators, DBAs, and managers, needs to read this book.”

Lisa Crispin, co-author of Agile Testing


“For many organizations Continuous Delivery isn’t just a deployment methodology, it’s critical to doing business. This book shows you how to make Continuous Delivery an effective reality in your environment.”

James Turnbull, author of Pulling Strings with Puppet


“A clear, precise, well-written book that gives readers an idea of what to expect for the release process. The authors give a step-by-step account of expectations and hurdles for software deployment. This book is a necessity for any software engineer’s library.”

Leyna Cotran, Institute for Software Research, University of California, Irvine


“Humble and Farley illustrates what makes fast-growing web applications successful. Continuous deployment and delivery has gone from controversial to commonplace and this book covers it excellently. It’s truly the intersection of development and operations on many levels, and these guys nailed it.”

John Allspaw, VP Technical Operations, and author of


The Art of Capacity Planning and Web Operations

“If you are in the business of building and delivering a software-based service, you would be well served to internalize the concepts that are so clearly explained in Continuous Delivery. But going beyond just the concepts, Humble and Farley provide an excellent playbook for rapidly and reliably delivering change.”

Damon Edwards, President of DTO Solutions and co-editor of


“I believe that anyone who deals with software releases would be able to pick up this book, go to any chapter and quickly get valuable information; or read the book from cover to cover and be able to streamline their build and deploy process in a way that makes sense for their organization. In my opinion, this is an essential handbook for building, deploying, testing, and releasing software.”

Sarah Edrie, Director of Quality Engineering, Harvard Business School


“Continuous Delivery is the logical next step after Continuous Integration for any modern software team. This book takes the admittedly ambitous goal of constantly delivering valuable software to customers, and makes it achievable through a set of clear, effective principles and practices.”

Rob Sanheim, Principal at Relevance, Inc.

From the Back Cover

Getting software released to users is often a painful, risky, and time-consuming process.

This groundbreaking new book sets out the principles and technical practices that enable

rapid, incremental delivery of high quality, valuable new functionality to users. Through

automation of the build, deployment, and testing process, and improved collaboration between

developers, testers, and operations, delivery teams can get changes released in a matter of hours—

sometimes even minutes–no matter what the size of a project or the complexity of its code base.


Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk

delivery process. Next, they introduce the “deployment pipeline,” an automated process for

managing all changes, from check-in to release. Finally, they discuss the “ecosystem” needed to

support continuous delivery, from infrastructure, data and configuration management to governance.


The authors introduce state-of-the-art techniques, including automated infrastructure management

and data migration, and the use of virtualization. For each, they review key issues, identify best

practices, and demonstrate how to mitigate risks. Coverage includes


• Automating all facets of building, integrating, testing, and deploying software

• Implementing deployment pipelines at team and organizational levels

• Improving collaboration between developers, testers, and operations

• Developing features incrementally on large and distributed teams

• Implementing an effective configuration management strategy

• Automating acceptance testing, from analysis to implementation

• Testing capacity and other non-functional requirements

• Implementing continuous deployment and zero-downtime releases

• Managing infrastructure, data, components and dependencies

• Navigating risk management, compliance, and auditing


Whether you’re a developer, systems administrator, tester, or manager, this book will help your

organization move from idea to release faster than ever—so you can deliver value to your business

rapidly and reliably.


Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index
Search inside this book:

Customer Reviews

4.2 out of 5 stars
Share your thoughts with other customers

Most Helpful Customer Reviews

6 of 6 people found the following review helpful By Sam Aspin on 14 Dec. 2011
Format: Hardcover
I was already familiar with the fundamentals of CI/CD and was interested in gaining a deeper understanding so I could put it to use in my own projects. I was hoping for some typical copy-paste style guide that would allow me to adapt the examples for my own use. However, that's not really what I got!

This book breaks down the fundamentals of Continuous Delivery (which arent much different to those of CI) into simple rules of thumb which as another reviewer pointed out wouldn't actually require that much space to list only once. What this book does instead is to explain in a very persuasive manner the reasons behind each of these rules and backs them up with real-life examples. I imagine I spent a lot of time nodding my head while I was reading this one.

Much of the book is made up of long-ish passages of text with the odd code-snippet and very few pictures, sounds rubbish, but trust me it's not! The code-snippets are written in a variety of languages but they provided the perfect starting point for me to go off and conduct my own research with the confidence I was looking in the right places.

Unlike many books this one may suggest a number of technologies for any given job and give you reasons to choose or not choose each. By following the principles in this book and adding a bit of my own research I was able to set up a fully-functional deployment pipeline using TeamCity and MSBuild. For my project I realised I wanted something even slicker than I had created and would probably require some outside help in order to achieve this. This book gave me an understanding of what I wanted that allowed me to quickly find the right man for the job and communicate exactly what I was after, firm in the belief that this would be money well spent!
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
29 of 33 people found the following review helpful By Augusto on 24 Jan. 2011
Format: Hardcover
I found the book extremely repetitive, to the point that after the 4th chapter I started skimming through it, as there's no point in reading it all. I don't know if the idea is to repeat phrases until the reader buys into them, or what. I'm quite disappointed that Martin Fowler put his signature on this book. Maybe they're a big happy family at Thoughtworks ... and hey, they need to make money out of Go.

I don't rate this book as just 1 star, as it has some good ideas, but it could have been written in 150 pages (max) rather than 450. Some of the concepts that are repeated until boredom are:
- Don't build the binaries at each stage of the deployment pipeline, create them once an reuse them.
- The capacity testing environment should be as similar as possible to the production environment.
- Script everything!
- Don't let builds that fail unit or acceptance test into production
- Put all the configuration in version control (network, firewall, OS, etc)

I also found the book more directed to manager who don't really know or care about the technology, but want to talk "in techie" language to their engineers. There are too few examples of how to use technology to build a deployment pipeline and most of the talk stays at a very abstract level.

My bottom line, I strongly suggest to read some blog posts and watch some presentations (check infoq) about this subject, it takes less time and it's more enriching than reading this book.
2 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
1 of 1 people found the following review helpful By M. T. Coote on 3 April 2011
Format: Hardcover
Readable and useful, practical content. The only gap is that there's not much information on the financial costs/benefits of the approach compared to more traditional methods. However, I wouldn't expect such data to be widely available yet.

There seems to be lots of merit in the approach described, not only in the build phase, but much more so in later lifetime stages of large systems, where most of the costs of ownership lie.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
3 of 4 people found the following review helpful By Amazon Customer on 26 Sept. 2010
Format: Hardcover
I wish I could have read this book years ago. It provides a comprehensive guide on how to go from software development to a working product, reducing the so called "cycle time", and at the same time reducing the risks always involved in releasing a software product in a production environment.
While describing the best practices in this field (mainly from the development point of view, but giving enough space to the Operations side), the authors don't limit them to specific scenarios, but keep the arguments generic enough to be applied to different development team sizes, product types, environment types. The main points are integrated with examples on actual projects which saw the authors involved: very useful to get a perspective on their point of view.
In my opinion the crucial point of this book is automated testing, which represents the first step towards the Continuous Delivery and "releasing with the push of a button".
Even if following all these concepts may be hard or not completely feasible for every project, knowing their existence and aiming to pragmatic satisfying them will lead to higher quality of the software and reduce the overall risk of releases.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
By Franck Mikulecz on 4 Nov. 2012
Format: Hardcover Verified Purchase
Rarely have I seen a book so full of teachings and so uniformly dense with knowledge. I have enjoyed it end-to-end and am here back for writing a review after quite a wile. The book will be accessible for business management people as well, and will give insight on the "why" as well as the how.
I mostly recommend it for teams of developers that are a bit cranky and stuck in their old ways.

The kind of book you buy multiple copies of, just to make friends or co-workers happy one day.
I would have appreciated it even as Christmas present !
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Recent Customer Reviews