The Phoenix Project by Gene Kim Continuous Delivery by Jez Humble Release It ! by Michael T. Nygard Web Operations by John Allspaw The Goal by Eliyahu. Continuous. Delivery. Jez Humble and David Farley. Upper Saddle River, NJ • Boston Continuous delivery: reliable software releases through build, test, and . What is Continuous Delivery? The ability to get changes into production or into the hands of users safely and quickly in a sustainable way.
|Published (Last):||25 August 2006|
|PDF File Size:||1.58 Mb|
|ePub File Size:||10.17 Mb|
|Price:||Free* [*Free Regsitration Required]|
Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Refresh and try again.
Continuous Delivery : Reliable Software Releases through Build, Test, and Deployment Automation
Open Preview See a Problem? Thanks for telling us about the problem. Return to Book Page. Preview — Continuous Delivery by Jez Humble. Winner of the Jolt Excellence Award! 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 deligery of the build, deployment, and testing process, and imp Winner of the Jolt Excellence Award! 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 confinuous 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 humblee 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.
Hardcoverpages. To see what your friends thought of this book, please sign up. To ask other readers questions about Continuous Deliveryplease depivery up. Ovidiu Neatu Language independent. Ravi This book is language independent.
It talks about principles and practices that can help you shorten the cycle of putting code from development into …more This book is language independent. It talks about principles and practices that can help you shorten the cycle of putting code from development into production.
As long as that’s your objective, it does not matter which language you are using.
See 2 questions about Continuous Delivery…. Lists with This Book. May 06, Yevgeniy Brikman rated it liked it. I’m a bit torn on this book: The biggest problem is the lack of real world examples. Chapters are mostly huge blocks of advice: There need to be far more examples of real world systems with both good approaches and bad approaches dis I’m a bit torn on this book: There need to be far more examples of real world systems with both good approaches and bad approaches discussed and compared in detail.
Moreover, the book is very very repetitive. Perhaps it’s from an attempt to make each chapter standalone, but while trying to find the new and interesting info in a new chapter, you have to wade through humblle of info you read many times in earlier chapters or even earlier paragraphs. There are many sentences, paragraphs, and even pages that can be skipped because they are obvious or just a rehash of something earlier or both. In short, this is a VERY important – perhaps even required – hkmble for anyone working on medium and large software projects, but this book desperately needs a tldr companion with lots of examples.
A few good quotes from the book: Without continuous integration, your software is broken until somebody proves it works, usually during a testing or integration stage. With continuous integration, your software is proven to work assuming a sufficiently comprehensive set of automated tests with every new change—and you know the moment it breaks and can fix it immediately.
For the software delivery process, the most important global metric is cycle time. This is the time between deciding that a feature needs to be implemented and having that feature released to users.
Do you do this on a repeatable, reliable basis? To paraphrase, cojtinuous is a measure of the time taken to process a single transaction, and can be measured either in isolation or under load. Throughput is the number of transactions a system humle process in a given timespan. It is always limited by some bottleneck in the system. The maximum throughput a system can sustain, for a given workload, while maintaining an acceptable response time for each individual request, is its capacity.
Customers are usually interested in throughput or capacity. When we talk about components, we mean a reasonably large-scale code structure within an application, with a well-defined API, that could potentially be swapped out for another implementation. A component-based software system is distinguished by the fact that the codebase is divided into discrete pieces that provide behavior through well-defined, limited interactions with other components.
Tim Dugan good points. Jul 13, This is the best book about Deployment I’ve hmble so far. Filled with lots of good advice for improvement and automation of a deployment process. I loved the concepts about deployments with no downtime and also found their maturity model a good guideline for improvement. I definitely recommend the reading for software development folks.
Jun 14, Michael Cotninuous rated it liked it. This book is considered a cornerstone of the DevOps movement.
In my opinion, it might be that in the very beginning, but currently most of the concepts that it presents are obvious and outdated. I will recommend it to be read to someone who’s new in the DevOps community, but if you’ve got a few years of experience in the area under your belt I would not. It’s nice to have all good concepts under one cover, but reading a pages long book that will tell you the history of GIT and SVN is pointless This book is considered a cornerstone of the DevOps movement.
It’s nice to have all good concepts under one cover, but reading a pages long book that will tell you the history of GIT and SVN is pointless in my opinion. Most of the ideas presented in the book could be wrapped in one long yet succinct blog post.
Mar 23, Eduards Sizovs rated it it was amazing. Feb 19, Serge Boucher rated it it was amazing. Apr 29, Chris Wood rated it it was amazing Shelves: Technologists operate in a fast-moving environment.
Languages rise and fall. Application strategies constantly shift across new hardware. Presentation layers move between thick and thin client across desktop, laptop, tablet, and phone architectures.
For that reason, technology writers produce materials that have a relatively short shelf life. Every now and then, books are published which make a lasting contribution to the field of computer science and software delivery i. Knuth’s Art of Comput Technologists operate in a fast-moving environment.
Knuth’s Art of Computer Programming or Brooks’ Mythical Man Month and find interested readers regularly pulling them off their shelves. Continuous Delivery by Farley and Humble is one such book.
Combining an uncanny vision for emerging technology trends, awareness of available delivery tools, massive experience in the realm of software delivery, and well articulated delivery strategies, the authors offer a relatively vendor-agnostic discussion of the delivery pipeline that ensures code quality, quick time-to-market, and painless release processes.
This book is highly relevant for anyone involved in the field of technology: Oct 25, Mark Seemann rated it did not like it Shelves: Some years ago, I had the fortune to attend Jes Humble’s workshop on continuous delivery. It was a good workshop, well delivered, and I learned a lot. I was, therefore, surprised that it turned out to be such a struggle to read this book.
It’s not that I disagree with the contents, but it’s so boring! Each page is mostly a wall of text, with no diagrams, sidebars, illustrations, or even bulleted lists. Even when there’s an occasional diagram, it seems strangely unhelpful.
While it could be that th Some years ago, I had the fortune to attend Jes Humble’s workshop on continuous delivery. While it could be that the material simply doesn’t lend itself easily to illustrations, I don’t think that’s the case.
As an example, on pagethe authors discuss the diamond dependency problem, but they use only text. If that isn’t an opportunity for an illustration, I jsz know what is. This particular problem is named after a shape the diamond shapeso it’d be a simple matter to add an illustration. The opportunity is missed, here, and many other places.
It’s not that I’m afraid of books without diagrams; I read lots of fiction. In a textbook that attempts to teach, on the other hand, I think the reader needs all the help s he can get to get through dry material. Such help is absent here. View all 3 comments. Jun 23, Harlen rated it liked it. The book successfully teaches the reader continnuous continuous delivery, the process and its benefits. Where this book stumbles is with the amount of repetition and lack of real-world examples.