Best practice: Ruleset versioning for every sprint - create blank RSV or create RSV only when there are rules in it?
Hello Experts, I would like to know your thoughts on which is a best practice or Pega recommended approach for creating rule set versions when moving code to other lower environments. I'm sure anything works well based on the need, but there should be some best or Pega recommended approach based on few considerations. Trying to understand that.
Say every 2 weeks code has to be packaged and moved to lower Envs using manual deployemnt(no CICD). In such scenario, among the 2 options below, what is the best approach and for what reasons?
Do you see creating blank RSVs as a overhead or do you see it as a clean way and easy to maintain?
if I may tag, for visibility @ericosman_GCS @CarissaW_GCS @MarcLasserre_GCS
Evoke Technologies
US
@NK2022 Hi, Basically we follow that once every ruleset is locked, based on the rule availability then we go with the creation of new ruleset version and we follow CICD.
For What reasons? (from my knowledge)
- Let's say even we have blank RSV overhead, then after package is moved, either we have to rename the RSV for another release or we have to delete and add a new one. (time consuming over here as well)
- Saves time while adding rulesets in product file.