Practice Continuous Deployability
Continuous integration doesn’t mean you have to deploy to production continuously. You don’t have to release every time someone checks in new code or at the end of every iteration. Releases should be determined by market demand, by supportability issues, by deployability issues, by version management, and things like that—not by development. Continuous deployability means you could release to production at any time, if you wanted to. When you actually release to production is a business decision.
All code and other files needed to build the system must be maintained in a version repository so as software is being built, developers are checking new features into version control and everybody works from a single ...
Get Beyond Legacy Code now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
