Table of Contents

Publishing a branch to a repository


Only available versions of this content are shown in the dropdown

If you are using a continuous integration and delivery (CI/CD) pipeline with third-party tools such as Jenkins, you can publish a branch from your development application to a Pega repository on the main development system (remote system of record) to start a merge.

To publish a branch to a repository, do the following steps:

  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.

    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.

  • Branches and branch rulesets

    Typically, you use branches in development environments in which multiple teams contribute to a single application. You use branches to develop software in parallel in a version-controlled environment. For example, your teams can develop one feature in a branch while another team develops a feature in a different branch, even if they share the sam

  • Integrating with file and content management systems

    File storage and knowledge management repositories store assets and provide versioning and metadata support. Pega Platform can communicate with common repository technologies and can also act as a binary repository.

Suggest Edit

Have a question? Get answers now.

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