- Overview
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- Packing projects into a package
- Analyzing a project
- Deploying a package to Orchestrator
- Running a job inside Orchestrator
- Testing a package or running a test set
- Testing multiple packages
- Deploying assets to Orchestrator
- Deleting assets from Orchestrator
- Running tasks using JSON configuration
- Restoring automation dependencies
- Troubleshooting UiPath CLI
- Azure DevOps extension
- Jenkins plugin

CI/CD integrations user guide
UiPath Solution Download Config
Application: Solution
Type: Post-Build task
UiPath Solution: Download Config is available in standard jobs and pipelines, and lets you download config for an UiPath solution package that was uploaded to an Orchestrator instance. This config can be edited with secret values that can later be used for deploy.
Solutions are currently supported only in Automation Cloud. Support for Automation Suite is planned for a future release. On-premises (MSI) Orchestrator does not support Solutions.
This task is compatible only with UiPath.CLI.Windows or UiPath.CLI.Linux at least version 25.10 or higher.
Configuration
| Job parameter | Description |
|---|---|
| Package Name | The name of the package for which config will be downloaded. |
| Destination Path | Path where the config file will be downloaded. |
| Package Version | Optional version of the package for which config will be downloaded. If omitted, config for latest version will be downloaded. |
| Destination File name | Optional parameter for setting a specific name to file without extension. If omitted package name will be used. |
| Format | Format of config file. Default value is yaml, but you could also specify json format. |
| Orchestrator address | The address of the Orchestrator instance where you'll download the config from. |
| Orchestrator tenant | Specify the Orchestrator tenant. |
| Authentication | For authentication towards Automation Cloud Orchestrator, you need to create credentials in Jenkins upfront. Solutions support External App authentication only. See Managing external applications for details on creating an External App and obtaining the required credentials. |
| Trace level | Setting used to enable trace logging to one of the following levels:
|
Pipeline example
pipeline { agent any environment { MAJOR = '1' MINOR = '0' } stages { stage ('Download Package Config File') { steps { script { orchestratorCredentials = ExternalApp( applicationId: 'External application identifier', applicationScope: 'AutomationSolutions Solutions.Deployments Solutions.Packages', applicationSecret: 'External application secret', accountForApp: 'Organization identifier' ) UiPathSolutionDownloadConfig( packageName: 'Package name', destinationPath: 'destination/path', packageVersion: '1.2.3', fileName: 'Local file name', format: 'yaml', orchestratorAddress: 'OrchestratorUrl', orchestratorTenant: 'Tenant name', credentials: orchestratorCredentials, traceLevel: 'Information', ) } } } }}pipeline { agent any environment { MAJOR = '1' MINOR = '0' } stages { stage ('Download Package Config File') { steps { script { orchestratorCredentials = ExternalApp( applicationId: 'External application identifier', applicationScope: 'AutomationSolutions Solutions.Deployments Solutions.Packages', applicationSecret: 'External application secret', accountForApp: 'Organization identifier' ) UiPathSolutionDownloadConfig( packageName: 'Package name', destinationPath: 'destination/path', packageVersion: '1.2.3', fileName: 'Local file name', format: 'yaml', orchestratorAddress: 'OrchestratorUrl', orchestratorTenant: 'Tenant name', credentials: orchestratorCredentials, traceLevel: 'Information', ) } } } }}