Skip to main content


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

Performing ad hoc tasks

Updated on July 14, 2022

By using ad hoc tasks, you can independently perform package and deploy actions outside of the context of a deployment, which is useful for exporting artifacts from the production environment and importing them into a lower environment, or for packaging and deploying artifacts if a Deployment Manager pipeline is not available.

Note: Ad hoc tasks are restricted to Super Admin users within Deployment Manager, or any user that has access to the Run ad hoc task privilege in Deployment Manager. If import conflicts are encountered when using ad hoc tasks, the conflict will always be overwritten.
Attention: Nexus repository is not supported with ad hoc tasks.
  1. If a pipeline is not open, in the navigation pane of Deployment Manager, click Pipelines and then click the name of a pipeline.
  2. From the navigation banner, click ActionsRun ad hoc tasks.
  3. In the Run ad hoc tasks window, select the target environment and an application-specific authentication profile pointing to the application for which you want to run an adhoc task.
  4. Select a task that you want to run on an artifact:
    • To package an artifact, on the Task menu click Package, and enter the repository name, product name, and version that you want to package.
    • To deploy an artifact, on the Task menu click Deploy, and enter the repository name and artifact path for the package you want to deploy.
  5. Select Execute task

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us