LinkedIn
Copied!

Table of Contents

Continuous integration and merging branches

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?

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.

Did you find this content helpful?

Have a question? Get answers now.

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