Image from Amazon Title: Continuous Delivery
Author(s): Jez Humble and David Farley
Publisher: Addison-Wesley Category: Build Tools
Amazon wrote: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.
I bought this book years ago and never finished reading it. The fact that it took me over 5 years to read it prevents me from giving it a higher review.
It's a good book with lots of concepts and good tips. There are a good number of stories to hold your attention. I felt like there was more repetition than necessary and the book didn't need to be 450 pages. I get that it is important to make those points. But maybe have them available as a quick reference at the beginning/end rather than continually “introducing them”. I like that the book was a mix of both higher level and lower level concepts. And that there were specific takeaways.