Table of Contents

Configuring systems in the pipeline


Only available versions of this content are shown in the dropdown

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.

To configure systems in the pipeline, do the following steps:

  1. Configuring authentication profiles

  2. Configuring the orchestration server

  3. Configuring candidate systems

  4. Creating repositories on the orchestration server and candidate systems

  • 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.

Did you find this content helpful?

Have a question? Get answers now.

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