Rule rebasing

If you are using continuous integration in a CI/CD pipeline with third-party automation servers such as Jenkins, after you merge branches, you can rebase your development application to obtain the most recently committed rulesets. Rebasing allows development teams working in separate development environments to share their changes and keep their local rule bases synchronized. Having the most recently committed rules on your development system decreases the probability of conflicts with other development teams.

For example, you publish a branch from your development application to a Pega repository on a remote development system. This action starts a job on your continuous integration tool, such as Jenkins, which merges branches. After the merge is completed, you can rebase the rulesets on your development application to obtain the merged rulesets.

For more information CI/CD pipelines, see the article Continuous integration and delivery pipelines using third-party automation servers on Pega Community.