Skip to main content

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

Continuous integration and merging branches

Updated on July 14, 2022

What is the correct way to make changes to non-rule-resolved rules and data?

At this point, NRR rules cannot be updated in branches. They need to be updated directly on the Dev (or remote dev) system). This will mean temporarily unlocking rulesets as needed and then re-locking, consistent with the versioning practices and development workflow

All NRR instances can be introduced in branches and have their ruleset updated accordingly upon being merged. When it comes to data instances, only Dynamic System Settings and Database Table rule types support this behavior by default.

In order to merge data instances of other classes, you must override the rule Embed-PegaAccel-Refactor-Instances-Merge!pyPopulateDataInstances.

For use with Deployment Manager, you also need to make sure your custom merge override is added to the production ruleset of the PegaDevOpsFoundation access group.

Can I use branches if my target application is locked?

Branches should never be added to the target application. Instead, add them to a team application. See Understanding development best practices in a distributed development environment with multiple teams for best practices.

How can I prevent my development branches from being migrated to higher environments?

Do not migrate your development branches to higher environments. Because branches are not included in the application package, your application might not perform as expected in higher environments.

Prevent the development branches from moving to the higher environments:
  1. Ensure that you do the following tasks:
    • Build your application stack in the following order:
      1. Create the production or main application.
      2. Build the test application on the base application.
      3. Build the development application on the test application.
    • Maintain branches in a development application to prevent the migration of branches to the higher environment.
    • Use the Check application compliance task, then and enable the Validate application branches parameter on the task to prevent the system from migrating branches. For more information, see Check application compliance.

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