Skip to main content

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

Understanding pipeline types

Updated on July 14, 2022

Pipeline templates help you structure pipelines for their ultimate purpose, as well separate business needs for better organizational efficiency. Deployment Manager offers four different pipeline types, each with a different use case. See the articles below for more information on the different available pipeline templates and their use cases.

  • Understanding deployment pipelines

    Deployment pipelines are an application pipeline type to generate artifacts from the system of record and deliver them through the various stages of the workflow. This pipeline template aligns with the continuous delivery (CI/CD) DevOps methodology, and deploys predictable, high-quality releases without using third-party tools.

  • Understanding merge pipelines

    Application developers make application changes and configurations that need to be integrated frequently with updates from other developers. These changes need to meet minimum standards of quality and compatibility ensuring that the changes made will not break existing functionality or cause a conflict with other changes. These users can leverage the merge pipeline template, built on the DevOps concept of Continuous Integration (CI).

  • Understanding business change pipelines

    Business change pipelines are used to support everyday, business-as-usual changes to your Customer Decision Hub (CDH) application. This pipeline type allows users to respond to changing requirements by modifying and deploying application rules in a controlled manner.

  • Understanding data migration pipelines

    Data migration pipelines are used to seek insight into how the changes that are made to decisioning logic affect the results of their strategies. To ensure that user simulations are reliable enough to help in making important business decisions, data migration pipelines can deploy a sample of the production data to a dedicated data migration test environment. This use case is powered by the data migration pipeline template. See for more information.

  • Understanding deploy artifact pipelines

    Use a deploy artifact pipeline to deploy an existing artifact that another pipeline created and validated. You can also deploy an artifact that one Deployment Manager instance generated to another Deployment Manager instance, for example, when there are two different Deployment Manager instances in the production and non-production environments.

  • Understanding update pipelines

    Keeping current enables your application to utilize the latest features, performance improvements, and security fixes to maximize customer success. Enhancing your Pega solution is now a simple and convenient process.

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