Take a photo of a barcode or cover
13 reviews for:
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
David Farley, Jez Humble
4.21 AVERAGE
13 reviews for:
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
David Farley, Jez Humble
4.21 AVERAGE
This book presents a good overview of the components needed to implement continuous delivery. It definitely got me thinking about the ways that my organization can improve our processes, but I fear that at times this book glosses over important details. I am reasonably sure that actually implementing changes like those described in the book will be fraught with pitfalls that I cannot anticipate and that were not covered in the book. I'm sold on the concept of continuous delivery, but I'm not confident in my ability to deliver it effectively.
It took me almost two years to finish the book, but I am happy that I did it today.
Continuous Delivery is a book that every agile team who wants to advance together should read. It is a handbook for every possible angle about delivering software continuously.
A team must first learn how to be agile. Estimating, planning, working together, following good engineering practices - these are tough adjustments for completely chaotic teams. But once a team feels like it has embraced agile, this is the exact book they should all read to make their software development cycle pain-free.
The book covers everything related to continually delivering working software: how to version control configuration, how to create a codebase that deploys identically to all possible environments, differing only by the config used for deployment, continuous integration, how to use a CI server to create a deployment pipeline, how to write good automated tests, how to write good automated ACCEPTANCE tests, pitfalls and challenges you might encounter while adopting Continuous Delivery practices, automating deployments, testing performance and security, manual testing, environment management, data management and migration strategies, version control, branching/merging, software componentization and dependency management, and a lot more.
If this seems like an awful lot to cover in a single book, it's because it is. The book is DENSE: absolutely packed with information. It's insight to word ratio is simply staggering. The only downside is that the book was written both to be read cover to cover as well as read piecemeal, which leads to repetition of information in some places. Since I read it cover to cover, this got mildly annoying, but it was pretty minor.
I was part of a team that was trying to adopt continuous delivery for the better part of two years. The book was not out at the time, and there were a lot of missteps and mistakes along the way. Our team learned a LOT of hard lessons about what works and what doesn't work to enable delivering software continually, and it was stunning to me just how much the book repeated, almost word-for-word, lessons that we learned in the process about the right way to do things. I know from first-hand experience that the advice offered in the book is rock-solid. I also know that the end-state, actually delivering working software through completely non-stressful deployments is a heavenly situation in which to work.
If your team is already agile and wants to take their delivery to the next level, I cannot possibly recommend this book highly enough. It's phenomenal.
A team must first learn how to be agile. Estimating, planning, working together, following good engineering practices - these are tough adjustments for completely chaotic teams. But once a team feels like it has embraced agile, this is the exact book they should all read to make their software development cycle pain-free.
The book covers everything related to continually delivering working software: how to version control configuration, how to create a codebase that deploys identically to all possible environments, differing only by the config used for deployment, continuous integration, how to use a CI server to create a deployment pipeline, how to write good automated tests, how to write good automated ACCEPTANCE tests, pitfalls and challenges you might encounter while adopting Continuous Delivery practices, automating deployments, testing performance and security, manual testing, environment management, data management and migration strategies, version control, branching/merging, software componentization and dependency management, and a lot more.
If this seems like an awful lot to cover in a single book, it's because it is. The book is DENSE: absolutely packed with information. It's insight to word ratio is simply staggering. The only downside is that the book was written both to be read cover to cover as well as read piecemeal, which leads to repetition of information in some places. Since I read it cover to cover, this got mildly annoying, but it was pretty minor.
I was part of a team that was trying to adopt continuous delivery for the better part of two years. The book was not out at the time, and there were a lot of missteps and mistakes along the way. Our team learned a LOT of hard lessons about what works and what doesn't work to enable delivering software continually, and it was stunning to me just how much the book repeated, almost word-for-word, lessons that we learned in the process about the right way to do things. I know from first-hand experience that the advice offered in the book is rock-solid. I also know that the end-state, actually delivering working software through completely non-stressful deployments is a heavenly situation in which to work.
If your team is already agile and wants to take their delivery to the next level, I cannot possibly recommend this book highly enough. It's phenomenal.
This is more for the people doing the work of creating the continuous delivery pipeline than for the non-technical troublemakers pushing for better processes.
This book was an interesting read and makes a pretty strong case for release early, release often, automate as much as possible. It had some good advice and examples of how to approach these problems, but some parts seemed to have addressed different (and unrelated) levels of abstraction. For example chapter on "Advanced Source Control" goes into history of source control while chapter on "Configuration Management" has examples of Puppet scripts in it. Admittedly these topics are interesting but don't have a direct relation to the subject of Continuous Delivery.
Continuous Delivery has become quite the buzz word lately. Hoping to start to better implement it at the office, I dug into this book.
This book goes through every single phase and offers examples and tips. I would consider this book an important theoretical read for every team attempting to implement this process.
This book goes through every single phase and offers examples and tips. I would consider this book an important theoretical read for every team attempting to implement this process.
Fantastic read; should be required reading for all developers and management in tech houses.
Can't wait to implement the arse out of this.
Can't wait to implement the arse out of this.
An excellent and thorough textbook that's well worth a read by anyone implementing or involved in Continuous Integration, Deployment and Delivery systems. A little dated as it tends to focus on Java and doesn't really discuss the impact of containers, but the principles are still clear and there are plenty of software orgs that don't follow the basic tenets laid out.
An excellent and thorough textbook that's well worth a read by anyone implementing or involved in Continuous Integration, Deployment and Delivery systems. A little dated as it tends to focus on Java and doesn't really discuss the impact of containers, but the principles are still clear and there are plenty of software orgs that don't follow the basic tenets laid out.