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.

Understanding systems in the Deployment Manager CI/CD pipeline

Updated on April 5, 2022

The CI/CD pipeline comprises several systems and involves interaction with various Pega Platform servers. For example, you can use a QA system to run tests to validate application changes.

Pipelines comprise the following systems:

  • Orchestration server – Pega Platform system on which the Deployment Manager application runs and on which release managers or application teams model and run their CI/CD pipelines. This system manages the CI/CD workflow involving candidate systems in the pipeline
  • Candidate systems – Pega Platform servers that manage your application's life cycle; they include the following systems:
    • Development system – The Pega Platform server on which developers build applications and merge branches into them. The product rule that defines the application package that is promoted to other candidate systems in the pipeline is configured on this system. Distributed development environments might have multiple development systems.

      In this environment, developers develop applications on remote Pega Platform development systems and then merge their changes on a main development system, from which they are packaged and moved in the Deployment Manager workflow.
    • QA and staging systems – Pega Platform servers that validate application changes by using various types of testing, such as Pega unit, regression, security, load, and performance testing.
    • Production system – Pega Platform server on which end users access the application.

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