Maintaining the CI/CD pipeline
As you may recall, in Chapter 10, Essentials of Production Release, we mentioned that a model is not the product; the pipeline is the product. Hence, after setting up automated or semi-automated CI/CD pipelines, it is critical to monitor the performance of our pipeline. We can do that by inspecting the releases in Azure DevOps, as shown in the following screenshot:
The goal of an inspection is to keep the CI/CD pipeline in a healthy and robust state. Here are some guidelines for keeping the CI/CD pipeline healthy and robust:
- If a build is broken, a fix it asap policy from the team should be implemented.
- Integrate automated acceptance tests.
- Require pull requests.
- Peer code review each story or feature.
- Audit system logs and events periodically (recommended).
- Regularly report metrics visibly to all the team members (for example, slackbot or...