Skip to main content

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

Creating a merge pipeline

Updated on December 13, 2021

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.

Add a new merge pipeline

To add a new pipeline, follow the steps below:

  1. Click Pipelines.
  2. Click New on the top right.
  3. Select the Merge pipeline template. Pipeline templates drive the required information needed to complete the creation of a pipeline. For more information, see Pipeline templates.
  4. Click Create after configuring the following sections on Application details, environment, and process model.
Note: Remember to save your configuration if you choose to navigate away from any of the pipeline creation screens. Progress will be lost if configurations are not saved.

Configuring a new pipeline - Application Details

Application Packaging Environment

  1. Specify the environment URL from where the rule branches are merged in the Application packaging environment field and select or enter the Authentication profile to be used for connection to the application packaging environment.

Application Details

Application details specify the application that this pipeline progresses through.

  1. In the Application field, select the name of the application.
  2. In the Version field, select the application version.
  3. In the Access group field, select the access group for which pipeline tasks are run.
    • This access group must be present on all candidate systems and have at least the sysadmin4 role.
  4. Skip the Product rule and Version field.
  5. In the Pipeline name field, enter a unique name for the pipeline.

Merge Policy

To configure the target ruleset version used when merging branches:

  1. In the Choose the target ruleset, field, select to use either the highest existing ruleset version, or input your own using the New ruleset version field.
  2. Enter the password for the ruleset version.
Enter a password for the merge policy.

Configuring a new pipeline - Environment Details


  1. Merge pipelines support a single stage by default, Development.
  2. Validate the Environment URL.
  3. If you are using your own authentication profiles, in the Authentication Profile field for the system, press the Down arrow key and select the authentication profile that you want to communicate from the orchestration server to the system.
    • By default, the fields are populated with the DMAppAdmin authentication profile.


  1. In the Artifact management section, specify the development and production repositories through which the product rule that contains application contents moves through the pipeline.
  2. In the Development repository field, select the development repository.
  3. Click Next.

Configuring a new pipeline - Model Pipeline

From the model pipeline screen, you can tailor your development stage by customizing the tasks.

  1. Stages can be modified here by clicking the More icon on each stage.
  2. You cannot add stages to a merge pipeline. For more information on the Development (Dev merge) stage, see Environment templates.
  3. To add a task to a stage, click the +Task button within a stage. The available tasks that you can add are specific to the associated stage. The available tasks that you can add are specific to the associated stage. For a list of task related information, see the Task catalog.
    1. The environment template assigned to a stage drives the availability of tasks. Mandatory tasks cannot be deleted.
    2. If you want to trigger a deployment pipeline to achieve continuous delivery, add a Trigger Deployment task after providing the pipeline ID for the deployment pipeline. For more information, see Trigger deployment.
      Enter a password for the merge policy.

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