Pega API to get branch conflicts returns Pega_API_029 (Missing Application) error code - PRPC 7.3
When i test the API call to check for conflicts (http://URL/prweb/api/v1/branches/<Branch name>/conflicts), this returns the error code Pega_API_029 (Missing application):
{
"pxObjClass":"Pega-API-CI-Branch"
,"errors":[
{
"ID":"Pega_API_029"
,"message":"Missing Application"
,"pxObjClass":"Pega-API-Error"
}
]
}
This error is not documented, and i cannot find any reference to this error in PDN.
I am trying to setup a build pipeline for Pega, using 7.3.x version (now with 7.3), but the first call i do to the API fails.
I called the method /branches/<branch name>/reviews, and created a review using the API, but getConflicts returns an error.
***Updated by moderator: Lochan to add SR details***
Hi, Can you please help us establish CI and CD using Bamboo CI tool. We need to perform the below steps and looking for help on the below items:
1. Locking the rule set and creating higher rule set version for next release using CI tools or some command line
You need to set the values for Param.ApplicationName and Param.ApplicationVersion in pySetApplicationDefaults Data Transform in Pega-API-CI-Branch.
If you are also going to merge, you're also need to update pySetVersionPasswordDefaults assuming you have a locked ruleset or want to lock your ruleset. (You really need to keep your rulesets locked at all times when using branches.)
Yes, exactly, i learned also this recently.
There is another Data Transform called pySetVersionDefaults, for the merge operation, to set the version of the Ruleset after merge.
Now, this works for me with 7.3.0.
On 7.3.1, they came up with a slightly different solution, with more parameters sent through the request.