Skip to main content


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

Creating pipelines

Updated on December 13, 2021

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.

If you have an existing pipeline, you can save it to a new pipeline for reuse. You can update the pipeline name, application name, and version when copying a pipeline.

See the articles below for more information on creating each of the available pipeline types.

  • Creating a deployment pipeline

    Deployment pipelines are an application pipeline type to generate artifacts from the system of record and deliver them through the various stages of the workflow. When you add a pipeline, you define all the stages and tasks that you want to do on each system. 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.

  • Creating a merge pipeline

    Merge pipelines enable developers to submit rule branches for a merge after validating the changes against specific quality gates such as guardrails, branch review, and automated tests. For example, if you are using branches, you can start a build when a branch is merged. Pipelines are the first step in getting started with setting up a process for deploying a change through the release.

  • Creating a business change pipeline

    Business change pipelines are used to support everyday, business-as-usual changes to your application. This pipeline type allows users to respond to changing requirements by modifying and deploying application rules in a controlled manner. When you add a pipeline, you define all the stages and tasks that you want to do on each system. Pipelines are the first step in getting started with setting up a process for deploying a business change outside of an enterprise release.

  • Creating a data migration pipeline

    Create a pipeline by defining the production and simulation environments and the application details for the pipeline. By using a data migration pipeline, you can export and import simulation data automatically.

  • Creating a deploy artifact pipeline

    Use deploy artifact pipelines to deploy an existing artifact that Deployment Manager validates. For example, use deploy artifact pipelines to deploy an existing artifact to a production or pre-production environment. You can also promote an artifact from one environment to another to update those environments to their most recent stage.

  • Creating an update pipeline

    Update pipelines automate and simplify near-zero-downtime updates by automating the basic update process. By using Deployment Manager as a standard DevOps approach during updates, you can promote the update fixes with ease to production and non-production environments through a single pipeline.

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.

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

Close Deprecation Notice
Contact us