Setting up repositories
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.
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.
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:
- 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
- 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.
- Test connection to ensure that the current system can connect to the target repository.
- 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.
Previous topic Quick-start guide for Deployment Manager on-premises and client-managed cloud Next topic Setting up the orchestrator