Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Understanding Deployment Manager architecture and workflows

Updated on April 5, 2022

Use Deployment Manager to configure and run continuous integration and delivery (CI/CD) workflows for your Pega applications from within Pega Platform. You can create a standardized deployment process so that you can deploy predictable, high-quality releases without using third-party tools.

With Deployment Manager, you can fully automate your CI/CD workflows, including branch merging, application package generation, artifact management, and package promotion to different stages in the workflow.

Deployment Manager supports artifact management on repository types such as Amazon S3, file system, Microsoft Azure, and JFrog Artifactory. Additionally, in Deployment Manager 3.3.x and later, you can create your own repository types; for more information, see Creating and using custom repository types for Deployment Manager. Deployment Manager also supports running automations on Jenkins that are not supported in Pega Platform such as running external regression or performance tests. In addition, Pega Cloud pipelines are preconfigured to use Amazon S3 repositories and are configured to use several best practices related to compliance and automated testing.

Deployment Manager is installed on the orchestration server, on which release managers configure and run pipelines. With Deployment Manager, you can see the run-time view of your pipeline as it moves through the CI/CD workflow. Deployment Manager provides key performance indicators (KPIs) and dashboards that provide performance information such as the deployment success rate, deployment frequency, and task failures. Use this information to monitor and optimize the efficiency of your DevOps process.

  • Understanding CI/CD pipelines

    A CI/CD pipeline models the two key stages of software delivery: continuous integration and continuous delivery.

  • Understanding systems in the Deployment Manager CI/CD pipeline

    The CI/CD pipeline comprises several systems and involves interaction with various Pega Platform servers. For example, you can use a QA system to run tests to validate application changes.

  • Understanding repositories in the pipeline

    Deployment Manager supports Microsoft Azure, JFrog Artifactory, Amazon S3, and file system repositories for artifact management of application packages. For each run of a pipeline, Deployment Manager packages and promotes the application changes that are configured in a product rule. The application package artifact is generated on the development environment, published in the repository, and then deployed to the next stage in the pipeline.

  • Understanding pipelines in a branch-based environment

    If you use branches for application development, you can configure merge criteria on the pipeline to receive feedback about branches, such as whether a branch has been reviewed or meets guardrail compliance scores.

  • Understanding pipelines in an environment without branches

    If you do not use branches for application development, but you use ruleset-based development instead, you configure the continuous delivery pipeline in Deployment Manager.

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