Skip to main content

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

Setting up repositories

Updated on December 13, 2021

Deployment Manager stores application artifacts created throughout the lifecycle of a deployment within a repository. Using Deployment Manager requires the usage of a supported artifact repository.

Missing brightcove video.

Note: Pega Cloud services issues clients with a default file storage repository with their instance of Deployment Manager. This article can be skipped for Pega Cloud clients, unless a custom artifact repository is desired.

Repository types

Pega Platform supports a variety of repository vendors. Deployment Manager packages and promotes the application changes that you configure in a product rule for each pipeline deployment. Deployment Manager generates the application package on the development environment, publishes to the repository, and deploys to each subsequent stage in the pipeline.

Note: Production-ready artifacts do not require their own repository. When a pipeline marks an artifact as production-ready, it copies the artifact from the development repository location to the production repository.

Deployment Manager supports the following repository vendors:

  • Microsoft Azure
  • JFrog Artifactory
  • Amazon S3
  • Nexus 2/3
  • File system

Deployment Manager does not support the following repository vendors:

  • Pega
  • defaultstore (repository instance included in each Pega deployment)

Pega provides the option to implement a custom repository type if required. For more information, see Creating and using custom repository types for Deployment Manager.


  • You have one of the listed supported repositories available
  • Candidate and orchestrator environments can access the repositories


  1. Log in to each candidate and orchestrator environment and create a repository record that connects to your desired artifact repository.
    • Ensure the same name is used for the repository on each environment.
    • For some repository types, such as JFrog and Nexus, you must select the Preemptive authentication check box on the Authentication Profile.
  2. Test connection to ensure that the current system can connect to the target repository.

Optional Steps

  • If you intend to use a separate repository for Production artifacts, create a second record pointed to the production repository on the development, production and orchestrator environments.

What to do next:

Previous: Installing or upgrading Deployment Manager 5.x

Next: Setting up the orchestrator

  • Previous topic Quick-start guide for Deployment Manager on-premises and client-managed cloud
  • Next topic Setting up the orchestrator

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