Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Rebasing rules to obtain latest versions

Updated on February 4, 2021

If you are using a continuous integration and continuous delivery (CI/CD) pipeline with Deployment Manager or third-party automation servers such as Jenkins, you can rebase your development application to obtain the most recently committed rulesets through Pega repositories after you merge branches on the source development system.

Before you begin: To rebase rules, you must first merge branches to make changes to rules. Changes made to rules in an unlocked ruleset version will not be visible by the rebase functionality.
Note: Only one rebase event at a time is supported per development system to prevent accidentally overriding a rebase event that is in progress.
Note: You can improve rebase performance by frequently incrementing the application patch version.
To rebase rules, complete the following steps:
  1. If you are migrating and merging branches separately, manually migrate branches for an application that has a new major or minor version. Rebase only pulls the ruleset version that is visible to your current application.
    For example: For example, if you previously migrated a branch for an application of version 1.x but are now working on a 2.x application version, migrate the 2.x branch ruleset to the main development system before rebasing. Otherwise, rebase refreshes your development system with the 1.x ruleset versions.
  2. In the header of Dev Studio click the name of your application, and then click Definition.
  3. On the Definition tab, click Get latest ruleset versions.
  4. In the Select repository list, select the repository from which to retrieve rules to see a list of ruleset versions that will be rebased.
  5. Click Rebase.
    • If there are no import conflicts, your development application is refreshed with the rules.
    • If there are import conflicts, the system displays them. For example, a conflict can occur if you made a change to the same ruleset version on your local development system or if you modified a non-resolved rule in the ruleset, such as the Application record. To resolve a conflict, complete the following step.
  6. If you have conflicts, you must resolve them before rebasing continues, either by overwriting or rejecting the changes on your development system. Complete the following steps to import the ruleset and either overwrite or reject the changes that you made to the ruleset on the development system:
    1. For each ruleset, click the Download Archive link and save the .zip file.
    2. Click the Click here to launch the Import wizard link at the top of the Rebase rule form to open the Import wizard, which you use to import the .zip files. For more information, see Importing rules and data by using the Import wizard.
    3. In the wizard, specify whether to use the older version of the ruleset or overwrite the older version with the newer version.
    4. After you resolve all conflicts, restart the rebase process by starting from step 1.
  • Previous topic Enabling ruleset versions for Pega repositories for rebasing
  • Next topic Understanding best practices for version control in the DevOps pipeline

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us