After you configure your automation server and your source development system, you can configure a pipeline on your job to automate the testing and merging of rules. Actions that you can do include obtaining merge conflicts, creating branch reviews, and running unit tests.

You can do the following actions:

• Send a notification with the job URL to the user who published the branch or started the job.
• Call the branches REST service with GET /branches/{ID}/conflicts to obtain a list of conflicts. If there are no conflicts, you can continue the job; otherwise, you can end the job and send a notification to the user to indicate that the job failed.
• Use the merges subresource for the branches REST service to merge branches.
• Call the merges REST service with GET /branches/{ID}/merge to obtain the status of a merge.
• Use the reviews subresource for the branches REST service to create a branch review.
• Use the Execute Tests service to run unit test cases or test suites. For more information, see Running test cases and suites with the Execute Tests service.
• Set up Jenkins to poll the job, using the unique ID that the branches service returned when you merged the branch, until the status is no longer set to Processing. If the merge is successful, you can continue the job; otherwise, you can send a notification to the user to indicate that the job failed.
• Publish the rulesets into which the branches were merged to a repository such as JFrog Artifactory.
• Notify the user that the job is complete.

For more information about the branches REST and merges REST services, seeImplementing a CI/CD pipeline with repository APIs.