We use Jenkins pipeline to move application from dev all the way to production. The RAP packages all the applications along wiht production rulesets. The issue we are facing is the pipeline overrides the delegated rule changes done in the production environment.
Dev team has no access to production, so we dont know what changed there.
To overcome this issue, I tried below approach:
Say ProdSupport:01-01-01 is what we are packing as a production ruleset in our application as a locked ruleset version.
We have ProdSupport:01-01-02 exists in production as an empty ruleset so that delegated rule changes can be saved here.
Issue I face is that the checkout button is no longer shown due to ProdSupport:01-01-01 locked.
Even if I keep it open, the rule is getting saved in to same verion.
Has anyone solved this issue in there projects having devops practise?
The best approach will be to separate the delegated rules into a separate application (and its associated ruleset). The Dev team will work on the core application, lets say AppCore 01.01 (and its associated rulesets, however the delegated rules will be part of AppDelegated 01.01 (and ruleset associated with that) that is built on top of AppCore 01.01. This way you can have a pipeline for Dev that migrates their latest changes to AppCore without impacting the delegated rules that is part of AppDelegated.
AppDelegated can be then updated independently either manually or with a separate Jenkins pipeline.