Helping a partner trying to diagnose an issue with their Merge pipeline. The issue is that all unit tests are running (and some failing, of course) on the “Run pega units on branch” task. Not sure if we’re just missing something in the doc, if it’s something that needs to be reported as an SR, or we should even be using this step.
The Deployment Manager Service Best Practices for merge pipelines references a different “Run Pega Units” task, allowing specification of a Test Suite ID.
Should we be using “Run Pega units on branch” at all? (The Deployment Manager Academy Challenge- a bit dated - instructions direct us to delete this step, saying it’s out of scope.)
Basically, the out-of-the-box setup in terms of steps. We preferred to use the run on branch option as it seems to make more sense for what we would like to achieve. Needing to add each unit test to a test suite prior to merging doesn’t seem like the best workflow.
This merge workflow is defined on the Dev version of our application. Our stack is basically Application, Application_Test, Application_Dev. The lowest level is intended for production, only trunk rulesets included, the test application includes test case rulesets, and the Dev application on top is where all branch based development happens prior to merging and therefore is where this merge pipeline is defined.
Our deployment pipeline is defined on the main application with reference to the test application and runs the non-branch version of unit testing task.
