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.

Adding a pipeline on Pega Cloud Services

Updated on April 5, 2022

If you are using Pega Cloud Services, when you add a pipeline, you specify details such as the application name and version for the pipeline. Many fields are populated by default, such as the URL of your development system and product rule name and version.

To add a pipeline on Pega Cloud Services, do the following steps:

  1. In the Designer Studio footer, click Deployment Manager.

  2. Click Add pipeline.

  3. Specify the details of the application for which you are creating the pipeline.

    1. To change the URL of your development system, which is populated by default with your development system URL, in the Development environment field, press the Down arrow key and select the URL.

      This is the system on which the product rule that defines the application package that moves through the repository is located.

    2. In the Application field, press the Down arrow key and select the name of the application.

    3. In the Version field, press the Down arrow key and select the application version.

    4. Click the Access group field and select the access group for which pipeline tasks are run.

      This access group must be present on all the candidate systems and have at least the sysadmin4 role. Ensure that the access group is correctly pointing to the application name and version that is configured in the pipeline.

    5. In the Pipeline name field, enter a unique name for the pipeline.

  4. Click Create.

    Result: The system adds tasks, which you cannot delete, to the pipeline that are required to successfully run a workflow, for example, Deploy and Generate Artifact. For Pega Cloud Services, it also adds mandatory tasks that must be run on the pipeline, for example, the Check guardrail compliance task and Verify security checklist task.
  5. Add tasks that you want to perform on your pipeline, such as Pega unit testing. For more information, see Modifying stages and tasks in the pipeline.

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