Links may not function; however, this content may be relevant to outdated versions of the product.
Creating and using custom repository types for Deployment Manager
In Deployment Manager 3.1.x and later, you can create custom repository types to store and move your artifacts. For example, you can create a Nexus repository and use it similarly to how you would use a Pega Platform-supported repository type such as file system. By creating custom repository types, you can extend the functionality of Deployment Manager through the use of a wider variety of repository types with your artifacts.
To create a custom repository type to use with Deployment Manager, complete the following steps:
Create a custom repository type. For more information, see Creating a custom repository type.
If you are using Deployment Manager 3.3.x or 4.1.x or later on each candidate system, add the ruleset that contains the custom repository type as a production ruleset to the PegaDevOpsFoundation:Administrators access group.
In the header of either Designer Studio (if you are using Deployment Manager 3.3.x) or Dev Studio (if you are using Deployment Manager 4.1.x or later), click.
In the Run time configuration section, click the Production Rulesets field, press the Down arrow key, and select the ruleset that contains the custom repository type.
Save the rule form.
Import the ruleset on which the custom repository is configured in to the orchestration system and add the ruleset to the PegaDeploymentManager application stack.
On the orchestration system, import the ruleset by using the Import wizard. For more information, see Importing rules and data by using the Import wizard.
In either the Designer Studio or Dev Studio header, in the Application field, click PegaDeploymentManager, and then click Definition.
On the Edit Application rule form, in the Application rulesetsfield, click Add ruleset.
Click the field that is displayed, press the Down arrow key, and then select the ruleset that contains the custom repository type.
Save the rule form.
Previous topic Configuring pipelines to use test cases Next topic Configuring Deployment Manager 4.x for Pega Platform 7.4