Publishing a branch to a repository

In a continuous integration and deployment (CI/CD) pipeline, you can publish a branch from your development application to a repository, which you can use to store and test branches.

If you are using CI/CD pipelines with third-party tools such as Jenkins, you can publish a branch to a Pega repository on the remote system of record (SOR) to start a merge. For more information about CI/CD pipelines and third-party tools, see the article Using continuous integration and deliery builds with third-party tools on Pega Community.
If you are using Deployment Manager and an SOR, and you have only one pipeline per application version, you can start a continuous integration build by publishing a branch to the SOR. You cannot publish a branch to start a build if you have multiple pipelines per application version, because you cannot specify the pipeline into which you want to publish and merge branches. For more information about Deployment Manager, see the article Deployment Manager on Pega Community.
Note: Branches that you submit into Deployment Manager pipelines can contain only the rulesets for the application that is associated with the pipeline.
  1. In the navigation panel, click App, and then click Branches.
  2. Right-click the branch that you want to push to a repository and click Publish to repository.
  3. In the Push branch to repository dialog box, select the repository from the Repository list.
  4. Click Publish.
    Result: You receive a message if the repository is not configured properly or is down, and you cannot push the branch to the repository.
  5. Click Close.