Continuous Delivery is a software development discipline where The book by Jez Humble and Dave Farley is the foundation book on this. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler)) [Jez Humble. 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):||15 December 2009|
|PDF File Size:||20.20 Mb|
|ePub File Size:||11.29 Mb|
|Price:||Free* [*Free Regsitration Required]|
Jul 13, Vlad Romanenko rated it it was amazing.
If this seems like an awful lot to cover in a single book, it’s because it is. Learn the patterns and practices used by high performing organizations to outcompete their peers.
I liked the analyses of common issues that I experience in my job, and sometimes I was happy to read the reasoning I couldn’t grasp myself. Nobody likes those tense weekends trying to get a system upgrade released before Monday dawns. Perhaps most importantly we remove one of the biggest sources of baleful stress in software development. Same thing is rehearsed throughout the book.
It’s nice to have all good concepts under one cover, but reading a jdz long book that will tell you the history of GIT and SVN is pointless This book is considered a cornerstone of the DevOps movement.
I loved the concepts about deployments with no downtime and also found their maturity model a good guideline for improvement. Everybody in IT should read this book, be he programmer, tester or operations specialist.
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. It was a good workshop, well delivered, and I learned a lot.
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
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 tons of info you read many times in earlier chapters or even earlier paragraphs.
I like how the book repeats over and over its core idea of having automated pipeline that makes feedback to developers faster and shorten the delivery cycle of working software. Jan 26, Kev rated it really liked it. Nov 25, Mac rated it really liked it. However deploying this new paradigm requires changes to both organizational culture and architecture.
What is Continuous Delivery? – Continuous Delivery
Although given it’s pages thick, the book could be more specific about dealing with credentials in production environments and data migrations.
Continuous Delivery by Farley and Humble is one such book. We also avoid the large amounts of re-work that plague the phased approach. Acknowledgements Jez Humble provided detailed help with this page. See 2 questions about Continuous Delivery…. 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.
I do agree with part of it.
Continuous Delivery builds on this, dealing with the final stages required for production deployment. Jun 23, Harlen rated it liked it. To paraphrase, performance is a measure of the time taken to process a single transaction, and can be measured either in isolation or under load.
Quotes from Continuous Delive It covers wide range of topics to support this idea. Lots of good material in here and parts of it are dated being 8 years later. The book successfully teaches the reader about continuous delivery, the process and its benefits.
Creating automated end-to-end functional acceptance tests is hard. Jul 13, This talk discusses how to take a lean approach to developing new products and running large scale programs of work, and how to grow a culture that enables organizations to turn software into a competitive advantage. Knuth’s Art of Computer Programming or Brooks’ Mythical Man Month and find interested readers regularly pulling them off their shelves. Businesses rely on getting valuable new software into the hands of users as fast as possible, while making sure that they keep their production environments stable.
This is due to a number of organizational factors, including culture, governance and financial management, and the application of portfolio and program management strategies that do not take advantage of the unique characteristics of software.
Long, high intensity releases become a thing of the past.
It is nice for overall understanding of CD, but nothing practical or immediately actionable. Languages rise and fall. This kind of delivery thinking has long been a forgotten corner of software development, falling into a hole between developers and operations teams. Continuous Delivery is sometimes confused jea Continuous Deployment. InformIT has made chapter five of the book available as a free download.