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. If the pipeline is not open, in the navigation pane, click Pipelines, and then 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 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.

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

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

   • Adding the Pega unit testing task
   • Adding the Jenkins task
   • Adding the Check guardrail compliance score task
   • Adding the Verify security checklist task
   • Modifying the Approve for production task

8. Click Finish.