Configuring pipelines and deploying applications in Deployment Manager
Use Deployment Manager to create continuous integration and delivery (CI/CD) pipelines, which automate tasks so that you can quickly deploy high-quality software to production.
On the orchestration server, release managers use the Deployment Manager landing page to configure CI/CD pipelines for their Pega Platform applications. The landing page displays all the running and queued application deployments, branches that are to be merged, and reports that provide information about your DevOps environment such as key performance indicators (KPIs).
- Navigating the Deployment Manager portal
The Deployment Manager portal is where you can find all information about pipelines and deployments. This portal offers functionality to filter pipelines, view reports, and view deployment statuses.
- Understanding pipeline types
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.
- Setting up users and roles
Define roles and users to manage which users can access Deployment Manager and which features they can access. For example, you can create a role that does not permit users to delete pipelines for a specific application.
- Creating pipelines
When you add a pipeline, you define all the stages and tasks that you want to do on each system. For example, if you are using branches, you can start a build when a branch is merged. If you are using a QA system, you can run test tasks to validate application data. Pipelines are the first step in getting started with setting up a process for deploying a change through the release.
- Configuring an application pipeline in 5.5.x
When you add a pipeline, you specify merge criteria and configure stages and steps in the continuous delivery workflow. For example, you can specify that a branch must be peer-reviewed before it can be merged, and you can specify that Pega unit tests must be run after a branch is merged and is in the QA stage of the pipeline.
- Interacting with application pipelines
Application pipelines are used to run deployments through Deployment Manager. See the following subsections on the various ways to interact with your pipeline types.
- Performing ad hoc tasks
By using ad hoc tasks, you can independently perform package and deploy actions outside of the context of a deployment, which is useful for exporting artifacts from the production environment and importing them into a lower environment, or for packaging and deploying artifacts if a Deployment Manager pipeline is not available.
- Troubleshooting issues with your pipeline
Deployment Manager provides several features that help you troubleshoot and resolve issues with your pipeline.
- Managing development standards
Policies help you enforce development best practices on the application by validating a selective list of high-value guardrail warnings. If Deployment Manager finds any violations, it throws an error and reports the rules in violation of the guardrail warning. Enforce a policy by adding the task to your pipeline. Using this feature reduces the risk of performance and security issues on Pega Platform or strategic application updates. This also helps you maintain an efficient, sustainable, and guardrail compliant application.
Previous topic Updating to the latest version of Deployment Manager Next topic Navigating the Deployment Manager portal