Release management has been always the boring part of software development. It is the discussion where people from different teams (operations, management, development, and so on) put all the details together to plan how to deploy a new version of one of the apps from the company (or various others).
This is usually a big event that happens at 4 a.m. in the morning, and it is a binary event: we either succeed in releasing the new version or we fail and have to roll back.
Stress and tension are the common denominators in these type of deployments, and above everything else, we are playing against the statistics.
In this chapter, you are going to learn how to create a continuous delivery pipeline and deploy a microservices-based system to update it, keeping all the lights on.
We will specifically cover the following topics:
- Playing against the statistics
- The test system
- Setting up a continuous delivery pipeline for images
- Setting up Jenkins