Skip to main content

Understanding repositories in the pipeline

Suggest edit Updated on April 13, 2020

Deployment Manager supports Microsoft Azure, JFrog Artifactory, Amazon S3, and file system repositories for artifact management of application packages. For each run of a pipeline, Deployment Manager packages and promotes the application changes that are configured in a product rule. The application package artifact is generated on the development environment, published in the repository, and then deployed to the next stage in the pipeline.

A pipeline uses development and production repositories. After a pipeline is started, the application package moves through the pipeline life cycle in the following steps:

  1. The development system publishes the application package to the development repository.
  2. The QA system retrieves the artifact from the development repository and performs tasks on the artifact.
  3. The staging system retrieves the artifact from the development repository and publishes it to the production repository.
  4. The production system deploys the artifact from the production repository
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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