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.
You can create multiple pipelines for one version of an application. For example, you can use multiple pipelines to use parallel development and hotfix life cycles for your application.
Application pipeline compatibility
|Candidate platform version||Orchestrator 4.8.4||Orchestrator 5.x|
|v8.1 - 8.5.1||Supported with PDF 4.8.4||Supported with PDF 4.8.4|
|v8.5.2+||Supported with PDF 5|
- Modifying an application pipeline
You can modify the details of your pipeline, such as configuring tasks, updating the repositories that the pipeline uses, and modifying the URLs of the systems in your environment. You cannot modify information if your pipeline is running.
- Pipeline templates
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.
- Environment templates
Environment templates are applied during stage creation and determine which tasks are added to a stage by default. Default stages and their associated environment templates are automatically added to your pipeline at the time of pipeline creation based on the type of pipeline created (merge, deployment, business change). You can modify the tasks for each stage on the Pipeline model screen.
- Task catalog
Deployment Manager supports a range of tasks to support the different application deployment scenarios for Pega powered applications. Tasks relevant to a use case are structured by environment templates and pipeline templates.
- Using multispeed deployments
Achieve greater flexibility over your pipeline workflow through multiple deployments that queue in the same stage of a pipeline. With this functionality, developers can regularly merge their changes for selective testing and promotion of deployments without blocking the pipeline. This approach introduces the concept of a transition between stages requiring user input to proceed.
- Archiving and activating pipelines
If your role has the appropriate permissions, you can archive inactive pipelines so that they are not displayed on the Deployment Manager landing page.
- Disabling and enabling a pipeline
If your role has the appropriate permissions, you can disable a pipeline on which errors continuously cause a deployment to fail. Disabling a pipeline prevents branch merging, but you can still view, edit, and stop deployments on a disabled pipeline.
- Managing artifacts generated by Deployment Manager
You can view, download, and delete application packages in repositories that are on the orchestration server. If you are using Deployment Manager on Pega Cloud Services, application packages that you have deployed to cloud repositories are stored on Pega Cloud Services. To manage your cloud storage space, you can download and permanently delete the packages.
- Deleting a pipeline
If your role has the appropriate permission, you can delete a pipeline. When you delete a pipeline, its associated application packages are not removed from the repositories that the pipeline is configured to use.
- Configuring application dependencies
Maintain small, reusable Pega applications with clearly defined, reusable functionality for ease of packaging for deployment. The multiple features for built-on applications allow you to enable multiple dependent applications for cross-functional feature reuse.