Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Understanding deployment pipelines for Pega Robot Manager applications

Updated on October 7, 2021

Learn how to build a deployment pipeline for Pega Robot Manager applications. By setting up your DevOps infrastructure, you can enable interaction between connected environments and deploy changes from one environment to another with just a few clicks.

Pega does not provide an out-of-the-box deployment pipeline model that is specific to Robot Manager applications. Use Deployment Manager to create a custom pipeline that reflects the deployment path for applications in your organization.
Tip: Deployment Manager contains a deployment pipeline template that you can use as a starting point. For more information, see Pipeline templates.

Pipeline customization tasks

After you complete the prerequisite steps as described in Preparing environments for deploying Pega Robot Manager applications, the following deployment tasks become available in Deployment Manager:

  • Migrate robotic packages – Exports the package binary file and the associated metadata from one environment to another.
  • Publish robotic artifacts to production – Promotes the robotic artifacts to the production repository.
  • Deploy robotic packages – Moves the robotic automation package files from the source to another repository and imports the associated metadata.

Configuration considerations

The following configuration example shows a simple pipeline for migrating Robot Manager applications. In Deployment Manager, each environment in the pipeline is called a stage. Each stage consists of a series of tasks that represent various steps in the application development.

A deployment pipeline template with additional robotic tasks
You adjust a default deployment pipeline template by using tasks that
                            enable migrating Pega Robot Manager applications

As a member of the Robot Manager deployment team, you can modify or extend the template to meet your business needs. Take the following factors into consideration, as referenced in the provided pipeline example:

  1. You can add the Migrate robotic packages task in the Development or any other custom stage, except for the Quality assurance, Staging, and Production stages.
  2. After you migrate automation packages to the target environment, you must deploy them by using the Deploy robotic packages task.
  3. Include the Publish robotic artifacts to production task only in the environment that immediately precedes the Production environment, for example, in Staging.
  4. The final deployment of automation packages in the Production stage must include the production-ready artifacts from the production repository.

Use the Robot Manager portal to initiate a deployment of your application from the first candidate environment in the pipeline (for example, the Development environment). For more information, see Initiating a deployment of Pega Robot Manager applications.

When your application moves past the initial deployment stage, you must use Deployment Manager to advance the application further in the pipeline, for example, from Quality Assurance to Staging. For more information, see Manually starting a deployment in Deployment Manager.

Note: You can use Robot Manager to get a read-only view of the deployment of your application as it is progressing through the pipeline beyond the initial stage.
    • Previous topic Preparing environments for deploying Pega Robot Manager applications
    • Next topic Initiating a deployment of Pega Robot Manager applications

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us