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.

Implementing a CI/CD pipeline with repository APIs

Updated on April 5, 2022

After you have configured an automation server and system of record (SOR) so that you can remotely start jobs on the automation server, you can implement a continuous integration and development pipeline with the branches REST and merges REST services. These services detect potential conflicts before a merge, merge rules in a branch, obtain the status of the merge, and create branch reviews. By remotely starting jobs that automatically perform branch operations, your organization can deliver higher-quality software more quickly.

To access the documentation about the data model, click ResourcesAPI.

For more information about response codes, see Pega API HTTP status codes and errors.

  • Understanding the branches REST service

    Use the branches REST service to retrieve a list of conflicts before you run tests and merge branches and perform additional tests on conflicts before performing a merge operation. You can also create branch reviews.

  • Understanding the merges REST service

    Use the merges REST service to obtain the status of the merge that you created by using the merge subresource.

  • Previous topic Configuring a continuous integration and delivery pipeline
  • Next topic Understanding the branches REST service

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