Jenkins CD design
In this section, we will go through a very general CD design.
Branching strategy
In Chapter 7, Continuous Integration Using Jenkins, we followed a branching strategy for the CI that included the following:
- The master branch
- The integration branch
- The feature branch
This branching strategy is a slimmer version of the GitFlow workflow branching model.
While CI can be performed on integration/development branches or feature branches, CD is carried out only on the integration and release branches.
The release branch
Some teams go with the strategy of having a release branch. A release branch is created after a successfully-tested code goes live in production (distributed to customers) from the master branch. The purpose of creating a release branch is to support bug fixes on the respective release:
Branching strategy
CD pipeline
We are now at the heart of the CD design. We will not create a new pipeline; instead, we will build on the existing CI Multibranch Pipeline in Jenkins. The new...