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, the Deployment Manager has all the necessary tasks and best practice workflows to deploy Pega Platform™ applications to production, merge changes, validate the changes by executing automated tests, and validate application quality metrics such as guardrails and test coverage and security configuration.
Deployment Manager allows application release managers to model a deployment pipeline using core Pega concepts such as stages and steps (tasks in the Deployment Manager).
The following image shows an example model-driven pipeline of a deployment process.
Types of pipeline templates
Pipeline templates offer a model-driven method to share the pipeline's best practices to simplify the process of adopting DevOps practices for a Pega Platform application.
In the following image, click the + icons to learn more about each pipeline template.
Environment template
An environment template is applied during stage creation and shows the tasks that the template must add by default to a stage. Environment templates supply the method to prescribe 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 on the environment templates, see Environment templates.
Check your knowledge with the following interaction.
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?