Close popover

Table of Contents

Understanding continuous integration and delivery pipelines with third party automation servers

Version:

Use DevOps practices such as continuous integration and continuous delivery to quickly move application changes from development, through testing, and to deployment. Use Pega Platform tools and common third-party tools to implement DevOps.

You can set up a continuous integration and delivery (CI/CD) pipeline that uses a Pega repository in which you can store and test software and a third-party automation server such as Jenkins that starts jobs and performs operations on your software. Use a CI/CD pipeline to quickly detect and resolve issues before deploying your application to a production environment.

For example, you can configure an automation server with REST services to automatically merge branches after you publish them to a Pega repository. You can also configure Jenkins to create branch reviews, run PegaUnit tests, and return the status of a merge.

  • Using branches with repositories in a continuous integration and delivery pipeline

    When you work in a continuous integration and development environment, you can configure a repository on a source development system to store and test software. You publish branches to repositories to store and test them. You can also configure a pipeline with REST services on your automation server to perform branch operations, such as detecting conflicts, merging branches, and creating branch reviews, immediately after you push a branch to the repository.

  • Remotely starting automation jobs to perform branch operations and run unit tests

    In a continuous integration and delivery (CI/CD) workflow, repositories provide centralized storage for software that is to be tested, released, or deployed. You can start a job remotely from an automation server, such as Jenkins, and use the branches REST and merges REST services to merge branches when you push them from your development system to a Pega repository on a source development system.

  • Implementing a CI/CD pipeline with repository APIs

    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.

Suggest Edit

100% found this useful

Have a question? Get answers now.

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