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 only minimizes manual error but also speeds up the software delivery process, enabling teams to react more swiftly to market demands. Having said that, in this chapter, we will extend our existing Jenkins CI pipeline to incorporate CD,...