You can modify the stages and the tasks that are performed in each stage of the pipeline. For example, you can skip a stage or add tasks such as Pega unit testing to be done on the QA stage.

Do the following steps:

1. Do one of the following actions:

   • If the pipeline is not open, in the navigation pane of Deployment Manager, click PipelinesApplication pipelines, and then click the name of the pipeline.
   • If the pipeline is open, click the name of the pipeline.

2. Click Pipeline model.

3. To specify that a branch must meet a compliance score before it can be merged:

   1. In the Merge criteria pane, click Add task.

   2. From the Task list, select Check guardrail compliance.

   3. In the Weighted compliance score field, enter the minimum required compliance score.

   4. Click Submit.

   For more information about compliance scores, see Compliance score logic.

4. To specify that a branch must be reviewed before it can be merged:

   1. In the Merge criteria pane, click Add task.

   2. From the Task list, select Check review status.

   3. Click Submit.

   For more information about branch reviews, see Branch reviews.

5. To run Pega unit tests on the branches for the pipeline application or for an application that is associated with an access group before it can be merged:

   1. In the Merge criteria pane, click Add task.

   2. From the Task list, select Pega unit testing.

   3. To run all the Pega unit tests for an application that is associated with an access group, in the Access Group field, enter the access group.

   4. Click Submit.

   For more information about creating Pega unit tests, see Creating Pega unit test cases

6. To start a deployment automatically when a branch is merged, select the Trigger deployment on merge check box. Do not select this check box if you want to manually start a deployment.

   For more information, see Manually starting a deployment in Deployment Manager.

7. Clear a check box for a deployment life cycle stage to skip it.

8. In the Continuous Deployment section, specify the tasks to be performed during each stage of the pipeline. See the following topics for more information:

   • Running Pega unit tests by adding the Run Pega unit tests task
   • Running Jenkins steps by adding the Run Jenkins step task
   • Specifying that an application meet a compliance score by adding the Check guardrail compliance score task
   • Ensuring that the Application Security Checklist is completed by adding the Verify security checklist task
   • Starting test coverage by adding the Enable test coverage task
   • Stopping test coverage by adding the Validate test coverage task
   • Running Pega scenario tests by adding the Run Pega scenario tests task
   • Refreshing application quality by adding the Refresh application quality task
   • Modifying the Approve for production task

9. Clear the Production ready check box if you do not want to generate an application package, which is sent to the production repository. You cannot clear this check box if you are using a production stage in the life cycle.

10. Click Finish.

11. Run diagnostics to verify that your pipeline is configured correctly.

    For more information, see Diagnosing a pipeline.