Skip to main content


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

Merging test rules into a merge pipeline

Updated on December 13, 2021

Merge test rules into a merge pipeline to practice continuous integration. Use the application structure that provides independent migration of your test and application artifacts, with the test application that is built on the main or production application (a locked and clean application).

  1. Create or edit, and then configure a merge pipeline as appropriate:
    ChoicesActions
    Create a merge pipeline
    1. Click Pipelines.
    2. In the upper-right corner of the page, click New, and then click Merge pipeline.
    3. Select the Merge pipeline template.
      For more information, see Creating a merge pipeline.
    Edit a merge pipeline
    1. In the navigation pane of Deployment Manager, click Pipelines, and then click the name of the pipeline.
    2. Click Actions Edit pipeline.
  2. On the pipeline model, click the Application details tab.
  3. Click the Configure application test cases checkbox to configure the merge pipeline to merge your test cases.
  4. In the Application field, in the Test application details section, enter or select the test application.
  5. In the Version field, enter or select the test application version.
  6. In the Access group field, enter or select the test application access group. See the following figure for an example
    Application test case configuration
    Configuration of test application details for merge pipelines
  7. Do one of the following actions:
    1. Click Save to save an existing pipeline.
    2. Click New to create a new merge pipeline.
For example:
Merge pipeline configuration
Configuration of test application details for merge pipelines

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us