Understanding continuous integration and delivery pipelines

DevOps is a culture of collaboration by development, quality, and operations teams to address issues in their respective areas. To sustain progress and bring continued improvement, tools and processes are put in place. Use DevOps practices such as continuous integration and delivery (CI/CD) pipelines to break down code into pieces and automate testing tasks, so that multiple teams can work on the same features and achieve faster deployment to production.

A CI/CD pipeline models the two key stages of software delivery: continuous integration and continuous delivery. In the continuous integration stage, developers can continuously merge branches into a target application. In the continuous delivery stage, the target application is packaged and moved through quality testing before it is deployed to a production environment.

You can set up a CI/CD pipeline for your Pega Platform application using one of two methods:

• Use third-party tools, such as Jenkins, to start a job and perform operations on your software. For more information, see the article Continuous integration and delivery pipelines using third-party automation servers on Pega Community.
• Use Deployment Manager, where you use Pega Platform as the orchestration server that runs the pipeline, packages your application, and manages importing packages from and exporting packages to repositories that connect from one system to another. For more information, see the article Deployment Manager on Pega Community.