Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring and running pipelines with Deployment Manager 3.4.x

Updated on December 13, 2021

Use Deployment Manager to create continuous integration and delivery (CI/CD) pipelines, which automate tasks so that you can quickly deploy high-quality software to production.

Use Deployment Manager to create continuous integration and delivery (CI/CD) pipelines, which automate tasks and allow you to quickly deploy high-quality software to production.

On the orchestration server, release managers use the DevOps landing page to configure CI/CD pipelines for their Pega Platform applications. The landing page displays all the running and queued application deployments, branches that are to be merged, and reports that provide information about your DevOps environment such as key performance indicators (KPIs).

Note: These topics describe the features for the latest version of Deployment Manager 3.4.x.

  • Configuring an application pipeline

    When you add a pipeline, you specify merge criteria and configure stages and steps in the continuous delivery workflow. For example, you can specify that a branch must be peer-reviewed before it can be merged, and you can specify that Pega unit tests must be run after a branch is merged and is in the QA stage of the pipeline.

  • Manually starting a deployment in Deployment Manager

    You can start a deployment manually if you are not using branches and are working directly in rulesets. You can also start a deployment manually if you do not want deployments to start automatically when branches are merged.

  • Starting a deployment in a distributed, branch-based environment

    If you are using Deployment Manager in a distributed, branch-based environment and using multiple pipelines per application, first export the branch to the source development system, and then merge it.

  • Completing or rejecting a manual step

    If a manual step is configured on a stage, the deployment pauses when it reaches the step, and you can either complete it or reject it. For example, if a user was assigned a task and completed it, you can complete the task to continue the deployment. Deployment Manager also sends you an email when there is a manual step in the pipeline. You can complete or reject a step either within the pipeline or through email.

  • Managing aged updates

    If your role has the appropriate permissions, you can manage aged updates in a number of ways, such as importing them, skipping the import, or manually deploying applications. Managing aged updates gives you more flexibility in how you deploy application changes.

  • Configuring settings to automatically apply schema changes

    You can configure settings to automatically deploy schema changes that are in an application package that is to be deployed on candidate systems. Configure these settings so that you do not have to apply schema changes if you do not have the privileges to deploy them.

  • Pausing and resuming deployments

    When you pause a deployment, the pipeline completes the task that it is running, and stops the deployment at the next step. Your user role determines if you can pause a deployment.

  • Stopping a deployment

    If a user has privileges to abort, they can do so to prevent a deployment from moving through a pipeline.

  • Managing a deployment that has errors

    If a deployment has errors, the pipeline stops processing on it. You can perform actions such as rolling back the deployment or skipping the step on which the error occurred.

  • Viewing branch status

    You can view the status of all the branches that are in your pipeline. For example, you can see whether a branch was merged in a deployment and when it was merged.

  • Viewing deployment logs

    View logs for a deployment to see the completion status of operations, for example, when a deployment moves from staging to production. When the Deploy task runs, the application package is imported in to the candidate system. By default, logs record all the new rule and data instances and all the updated rule and data instances that are in this application package. You can disable the logging of such rule and data types and can change the logging level to control which events are displayed in the log.

  • Viewing deployment reports for a specific deployment

    Deployment reports provide information about a specific deployment. You can view information such as the number of tasks that you configured on a deployment that have been completed and when each task started and ended. If there were schema changes on the deployment, the report displays the schema changes.

  • Viewing reports for all deployments

    Reports provide a variety of information about all the deployments in your pipeline. For example, you can view the frequency of new deployments to production.

  • Deleting a pipeline

    If your role has the appropriate permission, you can delete a pipeline. When you delete a pipeline, its associated application packages are not removed from the repositories that the pipeline is configured to use.

  • Viewing, downloading, and deleting application packages

    You can view, download, and delete application packages in repositories that are on the orchestration server. If you are using Deployment Manager on Pega Cloud Services, application packages that you have deployed to cloud repositories are stored on Pega Cloud Services. To manage your cloud storage space, you can download and permanently delete the packages.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us