-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Jenkins Administrator's Guide
By :

As we saw with the premerge CI pipeline, the static pipeline is only half of the challenge. Let's convert the static pipeline into a postmerge CD pipeline that is triggered by a GitHub PR merge.
The premerge pipeline runs when a PR is created or updated with a new commit. The postmerge pipeline runs when a PR is merged to a specific branch. Our postmerge pipeline bumps the version number and deploys an artifact, so it should only run when a PR is merged to the main
branch, not other branches. If the postmerge pipeline ran when a PR is merged to a branch other than main
, the version would be bumped and a new artifact would be deployed even though there are no changes to the artifact.
Create multiple postmerge pipelines if there are multiple active branches
A Git repository may have more than one branch from where the artifacts are versioned and deployed. These branches are sometimes called...