Question
Rulesware
CA
Last activity: 9 Feb 2021 15:05 EST
Retry a Branch Merge&Deployment after rejection/failure
Hello,
On Pega 8.2.5 and Deployment Manager 4.8.3. , Attempting to utilize the Branch Merge and deployment integration.
More often than not, we're getting a Merge Status "Rejected" with Status Message "Maximum attempts reached." , the issue seems a timeout similar to this thread ( https://collaborate.pega.com/question/when-branch-too-big )
The code on the branch is merged in the Dev environment, and branch is cleared. Apart from doing a manual trigger on the deployment manager to deploy the code. is there a way to retrigger the deployment from the dev environment ? or reattempt the same branch's rules ?
Updated: 28 Jan 2021 12:50 EST
Pegasystems Inc.
IN
Hi @Sari.alatif,
If I understand it correctly when you trigger branch merge, branch is getting merged but you are getting "Rejected" status and "Maximum attempts reached" message. Is it happening to you when you have more no.of rules in the branch or its intermittent?
Did you check the "Trigger deployment on merge" check box on pipeline model to automatically trigger the deployment on merge?
Rulesware
CA
It's intermittent. some branches would have 1 rule in them and still get that issue. and the "Trigger deployment on merge" is checked.
it works sometimes, branch is merged successfully in dev, and a product rule is triggered and deployed successfully. but other times it stalls and just gets the status mentioned "Maximum attempts reached", which led me to believe it's a network issue.
so either I increase the retry attempts or grace period, to give the system more time to connect , Or have some way from Dev side to retry the whole branch merge and trigger deployment process again.
Pegasystems Inc.
US
Hi @Sari.alatif,
In most cases when people see this timeout error, what is actually happening is an exception while saving the target application record. It would be helpful if you could take a look at the log on the SoR/Dev system the next time you encounter this error.
In most cases, these errors can be avoided by following the best practices outlined in the following discussion which advocate for creating a development layer for maintaining application branches: https://collaborate.pega.com/discussion/migrating-test-cases-separately
Thanks,
-Ryan
Accepted Solution
Rulesware
CA
After some more digging found the following :
The system checks for two DSS values to set the max retry count
@getDataSystemSetting("Pega-DeploymentManager","GetMergeStatusRetryCount","") @getDataSystemSetting("Pega-DevOps-ReleaseManager","GetMergeStatusRetryCount","")
If neither exists on system, it follows what was mentioned in ( https://collaborate.pega.com/question/when-branch-too-big ) answers.
The default behavior would be for the Deployment Manager to retry getting the "Merge Status" from the source environment 10 times with a 5 seconds wait in between.
Thanks,
-Sari