When you add a pipeline on premises, you define all the stages and tasks that you want to do on each system. For example, if you are using branches, you can start a build when a branch is merged. If you are using a QA system, you can run test tasks to validate application data.

• Adding the Pega unit testing task

  If you use Pega unit tests to validate application data, add the Pega unit testing task on the pipeline stage where you want to run it. For example, you can run Pega unit tests on a QA system.

• Adding the Jenkins task

  If you are using Jenkins to perform tasks in your pipeline, you can add the Jenkins task to the stage on which you want it to run.

• Adding the manual step task

  Use manual steps so that users must take an action before a pipeline deployment can continue. Users can either accept the task to continue the deployment or reject the task to stop it.

• Adding the Check guardrail compliance score task

  You can use the Check guardrail compliance score task so that an application must meet a compliance score for the deployment to continue. The default value is 95, which you can modify.

• Starting another pipeline by adding the Trigger deployment task

  You can start another pipeline by adding the Trigger deployment task to a stage in your current pipeline. By starting another pipeline from a current pipeline, you can add more stages to your pipeline.

• Adding the Verify security checklist task

  For your pipeline to comply with security best practices, you can add a task so that to ensure that all the steps in Application Security Checklist are performed.

• Starting test coverage by adding the Enable test coverage task

  Add the Enable test coverage task to start test coverage. Starting and stopping test coverage generates a report that identifies the executable rules in your application that are either covered or not covered by tests. As a best practice, to ensure application quality, you should test all the rules in your application for which testing is supported.

• Stopping test coverage by adding the Validate test coverage task

  Add this task to stop a test coverage session. Starting and stopping test coverage generates a report that identifies the executable rules in your application that are either covered or not covered by tests. As a best practice, to ensure application quality, you should test all the rules in your application for which testing is supported.

• Running Pega scenario tests by adding the Run Pega scenario tests task

  If you are using Pega scenario tasks, you can run them in your pipeline by using the Run Pega scenario tests task. Deployment Manager supports Selenium 3.141.59.

• Refreshing application quality by adding the Refresh application quality task

  To refresh the Application Quality dashboard, which provides information about the health of your application, on the candidate system, add the Refresh application quality task. You can refresh the dashboard after running Pega unit tests, checking guardrail compliance, running Pega scenario tests, and starting or stopping test coverage.

• Modifying the Approve for production task

  The Approve for production task is added to the stage before production. Use this task if you want a user to approve application changes before those changes are send to production.