Skip to main content

Understanding CI/CD pipelines

Suggest edit Updated on April 13, 2020

A CI/CD pipeline models the two key stages of software delivery: continuous integration and continuous delivery.

In the continuous integration stage, developers continuously validate and merge branches into a target application. In the continuous delivery stage, the target application is packaged and moved through progressive stages in the pipeline. After application changes have moved through testing cycles, including Pega unit, regression, performance, and load testing, application packages are deployed to a production system either manually or, if you want to continuously deploy changes, automatically.

Note: You should make changes only in the development environment and then move those changes to a higher environment. Do not make changes in any other environment.
Did you find this content helpful? YesNo

66% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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