Question

Merge Policy issue in Deployment Manager

Hi,

We have installed Deployment Manager on Pega 7.4. While configuring the merge policy to trigger deployment on branch merge, we can either merge into the highest existing ruleset version or create a new ruleset version.

However, while defining the product rule we need to mention ruleset versions that have to be packaged beforehand. If we want to merge into a new ruleset version, we cannot specify this in the product rule as this version does not exist.

How do we tackle this scenario?

Regards,
Namitha.

***Edited by Moderator Marissa to update platform capability tags****

Comments

Keep up to date on this post and subscribe to comments

Pega
April 3, 2019 - 6:10am

Under "Ruleset to Include" section in product rule ruleset versions are not mandatory. If you skip mentioning ruleset versions even new ruleset versions will be included in RAP.

 

 

April 4, 2019 - 11:52am
Response to gurrp1

Hi,

Let's say we only want to package a few ruleset versions as part of the release and in the merge policy we specify "create new ruleset version". In this case, how will it work?

 Thanks.

Pega
April 5, 2019 - 5:55am
Response to NAMITHAPISHE

Mention only minimum ruleset version to Product rule, this will include are versions from that minimum version to latest. 

April 8, 2019 - 5:13am
Response to gurrp1

Thanks. What if we need to package only the new ruleset version that gets created as per the merge policy?

Pega
April 8, 2019 - 5:41am
Response to NAMITHAPISHE

Deployment manager purely depend on product rule to package code and move to higher environments. Currently product rule don't have capability to package only latest version unless explicitly mentioned. Hence if you want to move latest version only then product rule should be updated with appropriate ruleset version.