Question
TCS
GB
Last activity: 4 Jul 2018 2:16 EDT
Pega Deployment Manager Configuration - Dev/SOR/Orchestration
Hi Pega!,
I'm trying to implement CICD pipeline in Pega Personal Edition 7.3.1.
I have configured two environments, one for Dev+SOR+Orchestration and another for QA.
I'm facing below issues,
- When I publish the branch to Pega repository, the below message is displayed,
"Branch was successfully published. The CICD process failed to import this branch"
-
Orchestration server is not automatically starting the "Merge Criteria" stage and hence the build is not triggering automatically (Checkbox is ticked to trigger the build on merge).
-
Branches are not showing up in "View Branches" after publishing from the Dev environment.
-
If I start the build manually, then "Generating Build" step keeps running forever (Log Attached).
Could you please help me resolve the issue?
Accepted Solution
Pegasystems Inc.
IN
Hi,
1)Is the pega repository configured on your Dev system pointing to the SOR and is it pointing to the pipeline application in SOR i.e the auth profile in the pega repository should login to the SOR in the pipeline application
2)Does the "HostedRulesetsList" DSS contain the ruleset present in the branch?
3)Atleast one ruleset version of the above ruleset should be locked on the SOR.Is it locked?
Pegasystems Inc.
IN
Hi,
Is RMURL DSS configured in your SOR which points to the release manager?
Your Dev+SOR+Orchestration is on a pega personal edition.is this server able to communicate to your QA system?
TCS
GB
Hi Mannj1,
1) Yes, RMURL is configured and it points to the release manager. As I'm using same environment for Dev, SOR and Orchestration, RMURL in SOR points to itself.
2) Yes, Dev+SOR+Orchestration can communicate with QA system. I'm running both the environments in the same network.
FYI, I have two applications in Dev/SOR/Orchestration system. One is for development and another is for Release Manager which is built on top of DeploymentManager application.
I have created four DSS as mentioned in the "Deployment Manager 01.01.02 and 02.01.02" Guide.
Pegasystems Inc.
IN
Hi,
1)When you configured your pipeline did you give for any of the URLS as "localhost".If yes please give IP address instead of localhost
2)The repositories you have configured for dev and prod repositories should be either "jFrog" or "S3".Is this repository instances present on all the systems?
3)do you have "ReleaseManager" auth profile on all the systems?Is this pointing to the Release Manager application which is built on top of deployment manager application?
TCS
GB
Yes Mannj,
1) I'm using IP addresses and not using "localhost" anywhere
2) I'm using JFrog repositories and it has been configured in both the systems. I can import/export artifacts from this repository without any issue
3) Yes, I've release manager auth profile pointing to the release manager application
TCS
GB
Hi Mannj,
I think there was a problem with search indexing. A step was failing while trying to open the instance of the Pipeline. After rebuilding the index, it worked.
Thanks!
Now the development stage is completed, the code is being deployed in QA. The deploying task is running for very long time and nothing is being traced in the tracer. Could you please help me in knowing what could've been possibly gone wrong?
TCS
GB
Hi Mannj!
The reason for the failure of deployment to QA was, the rules present in QA were the latest when compared with the rules present in the package to be deployed. This problem is resolved now.
As I have said in the main post, the first three issues still persists. The pipeline successfully completes only if I start the build manually. Please help me in finding out the reason, why CICD pipeline is failing to import the published branch.
To make it more clear, I'm publishing the branch from Dev application to Pega repository which is technically present in the same system. I've tried with the authentication profiles of both Dev application and Orchestration application.
Please correct me if I'm doing anything wrong here!
Accepted Solution
Pegasystems Inc.
IN
Hi,
1)Is the pega repository configured on your Dev system pointing to the SOR and is it pointing to the pipeline application in SOR i.e the auth profile in the pega repository should login to the SOR in the pipeline application
2)Does the "HostedRulesetsList" DSS contain the ruleset present in the branch?
3)Atleast one ruleset version of the above ruleset should be locked on the SOR.Is it locked?
TCS
GB
TCS
GB
When I publish a branch to the Pega repository, I'm getting this message "Branch was successfully published. The CICD process failed to clean up a stale version of this branch." I don't have any checked-out rules and I have locked the branch ruleset as well.
TCS
GB