Skip to main content

Creating a deploy artifact pipeline

Suggest edit Updated on December 11, 2021

Use deploy artifact pipelines to deploy an existing artifact that Deployment Manager validates. For example, use deploy artifact pipelines to deploy an existing artifact to a production or pre-production environment. You can also promote an artifact from one environment to another to update those environments to their most recent stage.

Before you begin: Ensure that you can connect to the repository from which the system passes the existing artifact to the deploy artifact pipeline. By default, the pipeline has two stages: Staging and Production. However, you can add more stages and use the Register artifact task as the first task in the first stage of the pipeline.
  1. In the upper-right of Deployment Manager portal, click New.
  2. Click the Deploy artifact pipeline template.

    Note: Pipeline templates manage the information that the system needs to complete the creation of a pipeline. For more information about pipeline templates, see Pipeline templates.

    Deploy artifact pipeline menu
    The New menu that shows the selection of the Deploy artifact
                                pipeline template .

Configuring application details for a deploy artifact pipeline

Add the application details for a deploy artifact pipeline.

  1. In the Application field, enter the name of the application.
  2. In the Version field, enter the application version.
  3. In the Access group field, enter the access group for which pipeline tasks are run.

    Note: All the candidate systems require this access group, which has at least the permissions for the sysadmin4 role.

  4. In the Pipeline name field, enter a unique name for the pipeline.

Configuring dependencies for a deploy artifact pipeline a deploy artifact pipeline - Dependencies

As a best practice, maintain applications so that they are small and reusable. Add multiple dependent applications to your applications so that you can reuse features that other teams develop. Use smaller applications with clearly defined reusable features to more easily package all the applications you are deploying in the pipeline.

Configure application dependencies to ensure that Deployment Manager always packages and deploys all your dependent applications, without needing to manually track or deploy the dependent applications to all your environments.

  1. In the Dependencies section, click Add.
  2. In the Application list, select the application name.
  3. In the Application version list, select the application version.
  4. In the Pipeline list, select the pipeline.
  5. In the Deployment list, select the deployment that contains the production-ready artifact of the dependent application.

    Note: If you want the latest artifact of the dependent application to be automatically populated, select latest.

  6. To add additional dependencies, click Add, and then repeat steps 2 through 5.

Configuring environment details for a deploy artifact pipeline

The default stages are populated based on the pipeline template that is created. For more information about pipeline templates, see Pipeline templates.

  1. In the Environment URL field for the system, press the Down arrow key, and then select the URL of the system.
    Note: By default, the Staging and Production stages are added to the pipeline. Update the environment URL and authentication profile for these stages.
  2. If you are using your own authentication profiles, in the Authentication Profile field for the system, press the Down arrow key, and then select the authentication profile that you want to communicate from the orchestration server to the system.
    By default, the fields are populated with the authentication profile.
  3. In the Artifact management section, specify the production repository where the publishes a validated application artifact.
    1. In the Production repository field, press the Down arrow key, and then select the production repository.
    2. Click Next.
  4. Add, remove, and modify stages in the pipeline model as appropriate.

    For more information on adding pipeline, see Modifying stages and tasks in the pipeline.

    Deploy artifact pipeline environment details
    The Environment Details stage of a deploy artifact pipeline that
                                shows the Staging and Production stages and corresponding
                                environment URL and authentication profile information.
  5. Click Create to save the pipeline.
  6. Run diagnostics to validate the health of your pipeline configuration.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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