Release approvals in a deployment

If the requirement is to allow a stakeholder to assess and approve the deployment before build acceptance or build promotion, the Perform manual step task can be added to the pipeline.
If the Perform manual step is configured on a stage, the deployment pauses when it reaches the step, and the user can either complete it or reject it if the user's role has the appropriate permissions.

The user has to complete the assigned task to continue the deployment. The Deployment Manager also sends an email when there is a Perform manual step task in the pipeline. The user can complete or reject a step either within the pipeline or through email.

For more information about how to complete or reject a manual step in the deployment, see Accepting and rejecting a deployment.

In multispeed deployments, the pipeline queues multiple deployments after the completion of a stage. You can use these deployments to promote to the next stage selectively. This functionality relies on the underlying pipeline model with the configuration that is available in Deployment Manager. When all tasks in a stage are complete, the stage progresses by using the Transition configuration. You can modify the transition setting to move to the next stage automatically or wait for a user action.

The landing page of the model pipeline provides a dashboard of all pending deployments within your application pipeline. From here, you can selectively promote deployments for progression through the workflow.

For more information about how to promote a deployment, see Using multispeed deployment.

Quality gates are pre-defined milestones where an application is assessed on the defined criteria which decide the outcome of the milestone. The purpose of quality gates is to ensure every application follows a set of defined rules and best practices to avert common risks and reduce the risk of failure.

You can configure a pipeline with the following tasks for quality control in the release process:

1. Use the Check guardrail compliance task to enforce a high quality and high performing application pass through the pipeline.
2. Use the Verify security checklist task to enforce the application security checklist completion to address the various security compliance practice on the application.
3. Use automated tests and rule coverage to assess the quality of application and testing with the help of tasks such as Enable test coverage, Run pega scenario (standalone selenium), Run pega unit tests, and Validate test coverage.

Check your knowledge with the following interaction.