LinkedIn
Copied!

Table of Contents

Modifying stages and tasks in the pipeline

Version:

Only available versions of this content are shown in the dropdown

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.

Stages

Version 5 of Deployment Manager supports more than four stages in a pipeline. If you are modifying an existing pipeline, you can perform the following steps for the desired results.

Add a new stage

  1. If the pipeline you wish to modify is not open, then click on Pipeline Application Pipeline.
  2. Click the pipeline name.
  3. From the Actions menu, click Edit pipeline. Ensure there are no active deployments in progress or awaiting action.
  4. Click Pipeline model.
  5. On this page, click the +Stage icon on the right of the flow model.
  6. Add a name to the stage.
  7. On the stage details section, add the mandatory parameters. For more information on the Environment template, see Environment templates.
  8. To enable multispeed deployment, select Wait for user action under the section labeled When all tasks in this stage are complete. For more information on multispeed deployment, see Using multispeed deployments in 5.1.x.
  9. Click Save.

Delete a stage

  1. If the pipeline you wish to modify is not open, then click on Pipeline Application Pipeline.
  2. Click the pipeline name.
  3. From the Actions menu, click Edit pipeline. Ensure there are no active deployments in progress or awaiting action.
  4. Click Pipeline model.
  5. On this page, click the stage you wish to delete.
  6. Click the More icon on the stage header.
  7. Click Delete stage.
  8. Click Save.

Tasks

Deployment Manager supports a range of tasks to support the different application deployment scenarios for Pega powered applications. Tasks relevant to a use case are structured by the following types:
  • Environment template: When the environment template on a stage is configured to anything other than custom, recommended tasks are populated for the environment template. A list of available tasks for the stage provides all tasks that can be added as necessary. When the environment template for a stage is custom, no recommendation or restriction applies to a stage. Users can choose any tasks from the tasks available in the system.
  • Pipeline template: Pipeline templates drive the range of tasks available though the environment type. Adding a task to a stage requires you to decide the step on which you want to add a stage and then follow the following steps:

    1. In the navigation pane of Deployment Manager, click Pipelines Application pipelines , and then click the name of the pipeline.
    2. Select the pipeline name. Click Actions Edit pipeline .
    3. On the pipeline model screen, identify the position where you need to add the task.
    4. Click the more icon on the task and click Add task below.
    5. From the task menu, select the task and click Select.
    6. Update the required task details.
    7. Click Save.
For more information on available tasks, refer to the Task catalog.

See below for a few different scenarios on using tasks to achieve different outcomes.

Scenario: Mandate a Guardrail compliance score of 100, with branch review before performing a merge.

  1. If the Merge pipeline is not open, in the navigation pane of Deployment Manager, click Pipelines Application pipelines , and then click the name of the pipeline. You can also filter on the pipeline template to narrow the search.
  2. Click Pipeline model.
  3. To specify that a branch must meet a compliance score of 100 before it can be merged:
    1. In the Development stage, click Check branch guardrail.
    2. In the Input parameters, add the desired score of 100 in the Threshold guardrail score.
    3. Click Save.
    For more information about compliance scores, see Check guardrail compliance.
  4. To specify that a branch must be reviewed before it can be merged:
    1. In the Development stage, click More on Merge task.
    2. Click Add Task Above.
    3. From the task list, select Check branch review status.
    4. Click Select.
    5. Click Save.
    For more information about branch reviews, see Branch reviews.

Scenario: Start a deployment after a merge is performed.

  1. If the Merge pipeline is not open, in the navigation pane of Deployment Manager, click Pipelines Application pipelines , and then click the name of the pipeline. You can also filter on the pipeline template to narrow the search.
  2. Click Pipeline model.
  3. To start a deployment automatically when a branch is merged:
    1. In the Development stage, click More on the Merge task.
    2. Select TriggerDeployment from the available task options.
    3. Click Select.
    4. In the task details panel, provide the Deployment pipeline ID.
    5. Click Save.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.