Continuous integration and delivery pipeline repositories

Repositories store assets and provide versioning and metadata support. In a continuous integration and delivery pipeline, repositories provide centralized storage for software that is to be tested, shipped or deployed. The Pega Platform can communicate with common repository technologies and can also act as a binary repository. The Pega Platform can browse, publish, or fetch artifacts that are created whenever an action creates a RAP: for example, exporting an application, product, branch, or component.

The repository is an instance of the Data-Repository class which holds all information required to connect to a repository.

Access to repositories is controlled by roles:

• PegaRULES:RepositoryAdministrator — The user can create, modify, and delete repository instances and browse and fetch contents from the repository. The PegaRules:SysAdm4 role includes this access.
• PegaRULES:RepositoryUser — The user can view repository instances and browse and fetch contents from the repository.

The Pega Platform includes wizards to create connections between the Pega Platform and the following repository types.

• JFrog Artifactory
• Amazon S3
• File system
• The Pega Platform acting as a binary repository. For more information, see Enabling the Pega repository type.

To create a connection with another repository type, create a custom repository type.