Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring an application pipeline

Updated on February 4, 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 in the following scenarios:

  • To move a deployment to production separately from the rest of the pipeline. You can then create a pipeline that has only a production stage or development and production stages.
  • To use parallel development and hotfix life cycles for your application.
  • Adding a pipeline on Pega Cloud Services

    If you are using Pega Cloud Services, when you add a pipeline, you specify details such as the application name and version for the pipeline. Many fields are populated by default, such as the URL of your development system and product rule name and version.

  • Adding a pipeline on premises

    When you add a pipeline on premises, 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.

  • Modifying application details

    You can modify application details, such as the product rule that defines the content of the application that moves through the pipeline.

  • Modifying URLs and authentication profiles

    You can modify the URLs of your development and candidate systems and the authentication profiles that are used to communicate between those systems and the orchestration server.

  • Modifying repositories

    You can modify the development and production repositories through which the product rule that contains application contents moves through the pipeline. All the generated artifacts are archived in the development repository, and all the production-ready artifacts are archived in the production repository.

  • Configuring Jenkins server information

    If you are using a Jenkins step, specify details about the Jenkins server such as its URL.

  • Specifying merge options for branches

    If you are using branches in your application, specify options for merging branches into the base application.

  • Modifying stages and tasks in the pipeline

    You can modify the stages and the tasks that are performed in each stage of the pipeline. For example, you can skip a stage or add tasks such as Pega unit testing to be done on the QA stage.

  • Previous topic Configuring and running pipelines with Deployment Manager 3.4.x
  • Next topic Adding a pipeline on Pega Cloud Services

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us