Deployment Rollback via Jenkins does not delete the ruleset version
Hi,
We are using Jenkins for deployments.
We have observed that in case of a failed deployment Jenkins triggers a rollback but the new ruleset version is not removed from the system.
We also observe that the Access Group does not update to the previous situation on restore point.
Our aim is to bring the system back to the same situation as it was when the restore point was created by Pega before the installation would have begun. How can this be achieved?
HCA Healthcare
US
@PiyushT In Pega, when using Jenkins for deployment, if a rollback is triggered due to failure, it doesn't automatically delete the newly created ruleset version or restore the access group to the previous state. To achieve a full rollback, including removing the new ruleset version and reverting access group settings, you need to explicitly configure the rollback steps in your Jenkins pipeline. This can be done by calling the Pega REST API for restore point management (/prrestservice/PegaMKT-Engine/v1/restorepoints) to revert the system to a saved restore point. Ensure that the restore point is created before deployment begins, and during rollback, invoke the restore API using the same restore point ID. Additionally, you may need to manually remove the newly imported ruleset version through a script or API if restore doesn’t automatically delete it, as restore only rolls back system state and not imported data.