Einar Fredriksen

55%
Flag icon
The intuitive objection to continuous deployment is that it is too risky. But, as we have said before, more frequent releases lead to lower risk in putting out any particular release. This is true because the amount of change between releases goes down. So, if you release every change, the amount of risk is limited just to the risk inherent in that one change. Continuous deployment is a great way to reduce the risk of any particular release. Perhaps most importantly, continuous deployment forces you to do the right thing (as Fitz points out in his blog post). You can’t do it without automating ...more
Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
Rate this book
Clear rating
Open Preview