Every change is, in effect, a release candidate. Every time a change is committed to version control, the expectation is that it will pass all of its tests, produce working code, and can be released into production. This is the starting assumption. The job of a continuous integration system is to disprove this assumption, to show that a particular release candidate is not fit to make it into production.
- Chapter 1. The Problem of Delivering Software
- from Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, Video Enhanced Edition
- Publisher: Addison-Wesley Professional
- Released: July 2010
=> Shouldn't have locks on Jenkins release candidates only being created by DevOps.
Share this highlighthttp://www.safaribooksonline.com/a/continuous-delivery-reliable/921014/