Hi,

I have tried your approach but faced no issue.

1. Added component ruleset to application

2. created branch and included above created ruleset.

3. saved a rule from application to branch and modified something later tried merging. 

May be something else you have done. Could you tell what error you got ?

Regards,

Upendhar V

What type of DevOps pipeline is being used? Is it Deployment Manager? If it is Deployment Manager is there a pipeline for that component?

Also, what version of Pega are you doing this in?

I am using Pega 8.1 version Deployment Manager and pipeline has been created for the same. Pipeline works fine for all other rulesets. Attached the screenshot of the error.

Can you confirm for me the version of Deployment Manager itself you are using? There have been two releases of Deployment Manager that is compatible with Pega Platform 8.1. 

From the error message it is clear that you have changes in the branch from a ruleset that is not in the application ruleset. There are a couple of ways to tackle this

a) If you are using DM version 3.4 or DM version 4.2, you can then merge a branch that has changes spanning the application layer 

b) If you are not using either of those releases, I would encourage you to upgrade to that, otherwise here is another approach. Ensure that you have changes in the branch for rulesets that are part of the application for which there is a pipeline. If your changes are for the component rulesets, then you will need to make sure that you add a pipelines just for the component app, make sure you are logged into the component app and then merge the branch from there.