Submitting a branch into a pipeline

If you are using Deployment Manager, submit a branch to your application to start the continuous integration portion of a continuous integration and delivery (CI/CD) pipeline. Branches that you submit into Deployment Manager pipelines can contain only the rulesets for the application that is associated with the pipeline.

If you are starting a branch locally, perform these steps on the local development system. If you are using a remote development system to merge branches, merge branches on the remote development system after you import them to the system.

For more information about Deployment Manager, see the article Deployment Manager on the PDN.

  1. Check all rules into their base rulesets before you merge them.
  2. Check if there are any potential conflicts to address before merging branches. For more information, see Viewing branch information.
  3. If you are using Deployment Manager on a remote development system, package the branch and then import it to the remote development system.
    1. Package the branch. For more information, see Packaging a branch.
    2. Impot the branch into the remote development system by using the Import wizard. For more information, see Importing a file by using the Import wizard.
  4. As a best practice, lock a branch after development is complete so that no more changes can be made. For more information, see Locking a branch.
  5. Check if there are any potential conflicts to address before merging branches. For more information, see Viewing branch information.
  6. Click App > Branches.
  7. Right-click the branch and click Merge.
  8. Click Proceed.
  9. In the Application pipelines section, from the Pipeline list, select the application for which the pipeline is configured into which you want to merge branches.
  10. Click Merge.
    The system queues the branch for merging, generates a case ID for the merge, and runs the continuous integration criteria that you specified in Deployment Manager.

    If there are errors, and the merge is not successful, an email is sent to the operator ID of the release manager that is specified on the orchestration server.