When you create a pipeline, Deployment Manager prompts you to categorize your pipeline and apply one of three templates. These pipeline templates help you structure pipelines for their ultimate purpose, as well separate business needs for better organizational efficiency.
Learn more about the different pipeline templates and their intended purposes.
Use a merge pipeline to merge any application changes to the system of record (SOR) as part of the continuous integration (C/I) DevOps methodology. Merge pipelines apply specific quality checks and guardrails to ensure that any changes that you want to merge have no negative impact on the SOR. If all merge criteria are successfully met, deployment can be triggered directly from the merge pipeline by adding a Trigger deployment task.
Deployment pipelines generate artifacts from the SOR 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.
Business change pipeline
A business change pipeline is a new pipeline type to support everyday, business-as-usual changes to your application. This pipeline template merges updates and generates a new application that exposes the latest changes. With this functionality, you can test the application with a small subset of users before activation, as well as roll back in the event of errors. Business change pipelines facilitate changing requirements by modifying and deploying application rules in a controlled manner.
Upgrade pipelines automate and simplify near-zero-downtime upgrades to promote the latest application functionality to your production environment. By using Deployment Manager as a standard DevOps approach during upgrades, you can assess the effect of the latest Pega Platform capabilities and plan your new feature adoption strategy across your environments after you upgrade to the latest version of Pega Infinity.