Skip to main content

Deployment process overview

A deployment pipeline in the Deployment Manager is an automated workflow that moves your application changes from development to production through different Stages, such as QA and staging. Each stage includes built-in checks, tests, and approvals to ensure quality and consistency.

Deployment pipelines automate repetitive steps and enforce quality gates for faster, reliable, and error-free deployments. This automation provides Release Managers and their teams with full control and visibility over the release process, which reduces manual effort and risk.

The deployment pipeline template supports the continuous delivery DevOps methodology by enabling predictable, high-quality releases.

For more information, refer to Understanding deployment pipelines.

Check your knowledge with the following interaction:

Deployment pipeline creation

As a service on Pega Cloud®, Deployment Manager is environment-agnostic. The system automatically registers all Route to Live (RTL) environments (Development, QA, UAT, and Production) and maps them to their corresponding pipeline Stages during pipeline creation.

When you create a deployment pipeline, you enter the application name, version, and product Rule. Deployment Manager uses these inputs to identify and package the application changes. These values also determine what the system exports from the source environment and deploys across each Stage in the pipeline.

Although optional, it is a best practice to configure a test application when you create deployment pipelines. The test application enables you to run automated tests on the main application.

Configuring the test application plays a crucial role in achieving high-quality application releases with faster time to market. For more information, see Creating a deployment pipeline

The following figure shows the default deployment pipeline model, which includes prepopulated Stages and Tasks that enforce best practices at every stage of deployment:

default deployment pipeline model is prepopulated with Stages and Tasks that help enforce best practices for creating and deploying your pipelines.

In the Deployment Manager service, you can modify environment labels, and customize the environment template to pre-configure the tasks on the  environments that are tagged to each stage on the pipeline. For more information, see Editing environments and Managing environments

Check your knowledge with the following interactions:

Starting a deployment

After creating a deployment, perform the following steps to start a deployment:

  1. Click the deployment pipeline that you created to open it.
  2. Click Start deployment for the pipeline.
  3. In the Start deployment dialog box, enter a description of the deployment.
    You can use this field to tag a deployment with a version note (such as alpha, beta, pilot, or Release Candidate (RC)).
  4. Click Submit.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice