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.

Modifying repositories

Updated on April 5, 2022

You can modify the development and production repositories through which the product rule that contains application contents moves through the pipeline. All the generated artifacts are archived in the Development repository, and all the production-ready artifacts are archived in the Production repository.

You do not need to configure repositories if you are using Pega Cloud Services; you can use different repositories other than the default ones that are provided.

Do the following steps:

  1. If the pipeline is not open, in the navigation pane, click Pipelines, and then click the name of the pipeline.

  2. Click ActionsArtifact Management.

  3. If you are using Deployment Manager on premises, or on Pega Cloud Services with default repositories, complete the following tasks:

    1. In the Application repository section, in the Development repository field, press the Down arrow key and select the development repository

    2. In the Production repository field, press the Down arrow key and select the production repository.

  4. If you are using Deployment Manager on Pega Cloud Services and want to use different repositories other than the default repositories, complete the following tasks:

    1. In the Artifact repository section, click Yes.

    2. In the Development repository field, press the Down arrow key and select the development repository.

    3. In the Production repository field, press the Down arrow key and select the production repository.

  5. Click Save.

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