Close popover

Table of Contents

Configuring an application pipeline

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 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.

Have a question? Get answers now.

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