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.
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?
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!
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?
1) Yes, the auth profile in the Pega repository is logging in to the pipeline application
2) I've included all rulesets, including the branch ruleset, in the "HostedRulesetsList" DSS
3) I made sure that all the ruleset versions are locked on the Dev
Just to be sure, when you say "SOR", it essentially means Dev in my case as I'm using the same system for both of them, right?
Also, how can we remove the stale version of a branch from Pega repository?
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.
Is it correct that the CICD pipeline triggers even when the branch is published to SOR, which is nothing but Dev? What are the other ways to trigger the pipeline? I'm unable to view branches from the release manager application. The pipeline is not starting after publishing the branch. When I looked at the logs, Target file path is empty. Please help me resolve this issue.