Skip to main content

Configuring an application pipeline in 5.3.x

Suggest edit Updated on December 13, 2021

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 lifecycles for your application.

Note: If you are using Deployment Manager for a release pipeline, the development or applicable stage responsible for artifact should not be at a higher version than the candidates where the artifact is planned for deployment. All candidate environments should have same versions of Pega platform.

Application pipeline compatibility

Candidate platform versionOrchestrator 4.8.4Orchestrator 5.x
v8.1 - 8.5.1Supported with PDF 4.8.4Supported with PDF 4.8.4
v8.5.2+Supported with PDF 5
  • Previous topic Deployment Manager 5.3.x archived documentation
  • Next topic Modifying URLs and authentication profiles in 5.3.x
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us