10
Planning for Continuous Deployment
In the previous two chapters, we took our initial steps into the world of Continuous Integration (CI) by setting up a CI pipeline in Jenkins. By automating the unit testing, Static Code Analysis (SCA), and build phases, we learned how we can significantly reduce the manual work involved in these stages and introduce a reliable way to catch issues early on. While CI handles the integration part of the development life cycle, it’s merely one side of the coin. The other side is Continuous Deployment (CD), which automates the delivery of code from the development environment into the production environment.
The essence of CD is to make deployments predictable, safe, and reversible. Automating this process not ...
Get Learning Continuous Integration with Jenkins - Third Edition 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.
