Pipeline templates
Deployment Manager offers a low-code and model-driven solution to manage application deployment processes through industry-standard Continuous Integration (CI), Continuous Delivery (CD), and Deployment patterns. Out of the box, Deployment Manager has all the necessary tasks and best-practice workflows to deploy Pega Platform™ applications to production, merge changes, validate the changes by running automated tests, and validate application quality metrics such as guardrails, test coverage, and security configuration.
Deployment Manager enables application release managers to model a deployment pipeline using core Pega concepts, such as stages and steps (tasks in the Deployment Manager).
The following figure shows an example model-driven pipeline of a deployment process:
Types of pipeline templates
In the following image, click the + icons to learn more about each pipeline template:
Pipeline templates offer a model-driven method to share the pipeline's best practices, which simplifies the process of adopting DevOps practices for a Pega Platform application.
Following are the different available pipeline templates:
Deployment pipeline
The Deployment pipeline template aligns with the Continuous Delivery (CD) DevOps methodology and deploys predictable, high-quality releases without third-party tools.
Deploy artifact pipeline
You can use this pipeline to deploy an existing artifact that was created and validated by another pipeline. You can also deploy an artifact that one Deployment Manager instance generated to another Deployment Manager instance.
Merge pipeline
The Merge pipeline applies specific quality checks and guardrails to ensure that any change you want to merge has no negative impact on the SOR. If all the merge criteria are successfully met, you can add a Trigger Deployment to trigger a deployment directly from the Merge pipeline.
Update pipeline
An Update pipeline simplifies the basic update process during a Platform update for Pega Infinity™. This pipeline outlines the update process and builds in the quality checks early in the update process to minimize the risk of update failures.
Business change pipeline
A Business change pipeline supports everyday, business-as-usual changes to the application. This pipeline template merges updates and generates a new application that exposes the latest changes. An advantage of this functionality is that you can test the application with a small subset of users before activation and roll back in the event of errors. The Business change pipeline facilitates the changing requirements by modifying and deploying application rules in a controlled manner.
Data migration pipeline
With the Data migration pipeline, to ensure that simulations are reliable enough to help you make important business decisions, you must deploy a production data sample to a dedicated data migration test environment.
Environment templates
You apply environment templates during stage creation, which show the tasks that the template must add by default to a stage. Environment templates supply the method for prescribing the best practices for a stage in the pipeline. Default stages and their associated environment templates are automatically added to the pipeline at the time of pipeline creation and are based on the type of pipeline created (Merge, Deployment, Business Change, and Data Migration). You can modify the tasks for each stage on the Pipeline model screen.
To learn more about environment templates, see Environment templates.
Check your knowledge with the following two interactions:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?