Creating a repository for continuous development

Create connections between Pega Platform and repositories to provide centralized storage, versioning, and metadata support for your application artifacts.

This content applies only to on-premises deployments and applications. For Cloud services and applications, an S3 repository is created fo ryou.

Note: To create a repository, your access group must have the PegaRULES:RepositoryAdministrator role. To use a repository, your access group must have the PegaRULES:RepositoryUser role.

The information you enter when you create the connection determines the file specification, also referred to as a file spec. A file spec is an alias, that is, a way to reference file locations that is independent of the physical file storage. A file spec is resolved based on configured file storages, such as repositories. You can view repositories with valid file specs on the File Storage landing page.

  1. In Dev Studio, click Create > SysAdmin > Repository.
  2. Enter a short description of the repository and the repository name and click Create and open.
  3. In the Definition tab, click Select and select the repository type.
  4. Configure your repository type by performing the following actions:
    • For JFrog Artifactory, go to step 5.
    • For Pega, go to step 6.
  5. Configure you JFrog Artifactory by performing the following actions:
    1. Click JFrog Articaftory.
    2. In the Repository key field, enter the root location on the JFrog server under which all artifacts are stored.
    3. In the Authentication profile field, specify Basic.
    4. In the Host ID field, enter the location of the JFrog deployment.
      Note: Do not include any text after the host address that starts with /artfiactory. For example, if a JFrog deployment is accessed through https://10.35.324.324:8081/artifactory, the value entered in the Host ID field must be https://10.35.324.324:8081.
  6. For on-premises deployments, configure your Pega repository by performing the following actions. For Pega Cloud applications, a repository is created and configured for you during provisioning.
    Note: The Pega repository type is shown only if you are using the Deployment Manager, otherwise, you must enable it. For more information, see Enabling the Pega repository type.
    Note: Do not use Pega repositories if you are using Deployment Manager with multiple pipelines per application version. You receive an error and cannot publish the branch into the application, because you cannot select the pipeline into which you want to publish and merge branches. Instead, use the Merge Branches wizard to start pipelines. For more information, see Submitting a branch into a pipeline.
    1. Host ID – The location of the Pega node. It must start with http:// or https:// and must end with PRRestService. For example:
    2. Optional: In the Use authentication section, specify whether the repository authenticates the user.
    3. Optional: In the Authentication Profile section, specify the authentication profile. If there is no authentication profile, the username must have PRPC:Administrators as an access group.
    4. In the Security section, configure security:
      Secure protocol
      the lowest level of security that can be used. If this minimum level of security is not available, the repository call fails with an error message.
      a Truststore record that contains the server certificate to use in the TLS/SSL handshake.
      a Keystore record that stores the Pega Platform client's private/public key pair that is used by the server to authenticate the client.
  7. Click Test connectivity to verify the credentials.
  8. Click Save.