Page History

...

1. Only Jenkins Admin can update the pipeline with the release branch & trigger build on the pipelines
2. Verify if the release branch is scanned by the pipeline (for eg Jenkins → NightlyTests pipeline → Branches should reveal the release branch).
3. If the branch doesn't exist, trigger a branch scan using "Scan Repository now" (this should scan all the branches that meet the criterion mentioned in Configure → Branch Sourches → Behavior)
4. If branch is still not added, then manually add the release branch by updating the criterion
   
   1. Once logged in to Jenkins, Configure -> Branch Sources -> Behavior -> Append release branch E.g. (
   1
   1. v1.7.x)
5. Trigger a build manually (if needed)  <Pipeline> -> 1.7.x -> Build Now

Note : Currently (master)|(^v.*) ensures all release branches starting with v should be scanned & included into the pipeline.

Backward Compatibility checker (currently restricted).

...