Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Migrating and merging branches with third-party automation servers

Updated on September 10, 2021

If you are using a third-party automation server such as Jenkins, you can automatically start a branch merge after you publish it to the development source system.

To publish a branch and automatically start a merge, do the following tasks:

  1. Create a Pega repository connection between the remote development system and the development source system. For more information, see Adding a Pega repository.
  2. Configure the pyPostPutArtifactSuccess activity to merge branches automatically after publishing them to the development source system. For more information, see Configuring the pyPostPutArtifactSuccess activity.
Note: Ensure that you add and configure a step with the Call pxImportArchive method to import the application package after you publish it to the development source system. If you do not, the package is only  copied to the service export directory.
  1. Publish the branch to the development source system through the Pega repository. For more information, see Publishing a branch to a repository.

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