Question
Citigroup Inc
IN
Last activity: 30 Aug 2018 14:48 EDT
Trigger build on merge branch - Status showing not started in Pega 7.4
Hello,
I am working on CICD configuration in Pega 7.4 env using deployment manager version 3.2. I have configured the test pipeline for test application. It is working fine when I run the build manually from orchestration server. But when I am merging branch in application, it is showing merge status as Resolved-PipelineQueued. When I am checking the status in pipeline by clicking Action > View Branches, it is showing merge status as "Not Started". Can someone advise, what else I need to do?
Regards
Ragahvendra
Pegasystems Inc.
IN
Hi Raghavendra,
Please verify that "Trigger deployment on merge" flag is checked in your pipeline model. If yes, this may require some further troubleshooting. I request you to directly reach out to [email protected] with this request, and our team will help you out with this.
Best regards
Updated: 30 Aug 2018 14:47 EDT
Pegasystems Inc.
US
Hi Raghavendra,
If you see "Not Started" on the Merge Status in Actions > View branches, it suggests to me that you were successfully able to kick of the "Merge criteria" CI Stage, but it is stuck in the pxStartCIProcess flow. I believe that we rely on the agent that manages SLAs to continue the flow. I believe that it is called "ServiceLevelEvents."
- You might want to check to see if ServiceLevelEvents agent is currently running. If not, something might be wrong with your system and I would start troubleshooting with a restart.
- If ServiceLevelEvents is running, please have a look at the Queue Management landing page to see if there are any broken System-Queue-DefaultEntry items. If so, please click on the hyperlink to view an XML Preview and send that XML to [email protected]
- If there are no broken System-Queue-DefaultEntry items, I'd be curious to hear about the state of your work object. If you could open the work object in the class Pega-Pipeline-CI-<AppName><PipelineName> and let us know if there are any assignments on that work object and sending a screenshot of the audit tab to [email protected] might be helpful.
Thanks,
Dave