Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring systems in the pipeline

Updated on February 4, 2021

Configure the orchestration server and candidates in your pipeline for all supported CI/CD workflows. If you are using branches, you must configure additional settings on the development system after you perform the required steps.

  • Configuring authentication profiles

    Deployment Manager provides default operator IDs and authentication profiles. You must enable the default operator IDs and configure the authentication profiles that the orchestration server uses to communicate with the candidate systems.

  • Configuring the orchestration server

    The orchestration server is the system on which the Deployment Manager application is installed and release managers configure and manage CI/CD pipelines. Configure settings on it before you can use it in your pipeline.

  • Configuring candidate systems

    Configure each system that is used for the development, QA, staging, and production stage in the pipeline.

  • Creating repositories on the orchestration server and candidate systems

    If you are using Deployment Manager on premises, create repositories on the orchestration server and all candidate systems to move your application between all the systems in the pipeline. You can use a supported repository type that is provided in Pega Platform, or you can create a custom repository type.

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