Branch merging

After teams have completed rule development in a branch, you can use the Merge Branches wizard to move the contents of the branch into the base ruleset of the development application.

For more information about merging branches into target rulesets in an application, see Merging branches into target rulesets.

In addition, if you are using Deployment Manager, you can start a continuous integration and delivery (CI/CD) pipeline by using the Merge Branches wizard. You can submit a branch to your application and start the CI portion of the pipeline when the following criteria is met:

You have created a pipeline for your application in Deployment Manager.
You are merging a single branch.
The RMURL dynamic system setting, which defines the URL of orchestration server, is configured on the system.
All the rulesets in your branch belong to a single application that is associated with your pipeline. Therefore, your branch cannot contain rulesets that belong to different application layers.

Note: When you submit a branch into a CI/CD pipeline, you do not need to provide target ruleset versions or lock passwords, and you cannot save the contents of the branch. These features are configured in Deployment Manager.

For more information about submitting a branch into a pipeline, see Submitting a branch into a pipeline.

For more information about Deployment Manager, see the article Deployment Manager on Pega Community.