Skip to main content


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

Adding a pipeline on Pega Cloud Services

Updated on December 13, 2021

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 navigation pane, click PipelinesApplication pipelines.
  2. Click New.
  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. If you are using a separate product rule to manage test cases, to deploy a test case, in the Application test cases section, select the Deploy test applications check box; then, complete the following steps:
    1. In the Test application field, enter the name of the test application.
    2. In the Version field, enter the version of the test case product rule.
    3. In the Access group field, enter the access group for which test cases are run.
    4. In the Product rule field, enter the name of the test case product rule.
    5. From the Deploy until field, select the pipeline stage until the test case product rule will be deployed.
      Note: When you use separate product rules for test cases and run a pipeline, the Run Pega unit tests, Enable test coverage, and Verify test coverage tasks are run for the access group that is specified in this section.

      For the Run Pega scenario tests task, the user name that you provide should belong to the access group that is associated with the test application.

  5. To change product rule that defines the contents of the application, the Product rule field, enter the name of the product rule that defines the contents of the application, which is populated by default with the application name.
  6. To change the product rule version, in Version field, enter the version, which is populated by default with the application version.
  7. 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.
  8. Add tasks that you want to perform on your pipeline, such as Pega unit testing.
  9. Run diagnostics to verify that your pipeline is configured correctly.
    For more information, see Diagnosing a pipeline.

Tags

Pega Platform 8.6 DevOps

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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