- Overview
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- Test Manager Support
- Packing projects into a package
- Signing project packages
- 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 Deploy
The UiPath Solution Deploy task deploys a UiPath solution package onto UiPath Orchestrator. This creates a deployment of a solution package in a specific environment and folder structure.
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.WindowsorUiPath.CLI.Linux` at least version 25.10 or higher.
Configuration
Use the following table to configure the UiPath Solution Deploy inputs.
| Parameter | Description |
|---|---|
| Orchestrator connection (Required) | A service connection to the Orchestrator instance onto which the package will be deployed. |
| Package Name (Required) | The solution package name from Orchestrator. |
| Package Version (Required) | The solution package version from Orchestrator. |
| Deployment Name (Required) | The name of the deployment to create or upgrade. |
| Deployment Parent Folder | Optional. The Orchestrator folder where the deployment folder will be created. If not specified, the deployment folder will be created in tenant folder. When specified, deployment will be under respective folder. When set to "[email protected]'s workspace", the deployment will be under personal workspace for specified user. |
| Deployment Folder (Required) | The name of the deployment folder where solution files will be placed. |
| Configuration File Path | Optional. The path to a configuration file to be used during deployment. If not specified, the default configuration file associated with the solution package will be used. |
| Trace Level | The trace logging level. Default: Error. Options: None, Critical, Error, Warning, Information, Verbose |
If a deployment with the same name already exists at any level within the tenant in Orchestrator, this operation upgrades the existing deployment instead of creating a new one. If the existing deployment is in Failed state, the upgrade does not proceed; resolve or uninstall the failed deployment before retrying.
Solutions deployed at the tenant level do not automatically assign a user to the resulting folder. To assign an account, ensure the appropriate configuration is set in Orchestrator (Tenant > Folders).
Notes
- Solution deployment: This task creates deployments of solution packages in specific Orchestrator environments.
- Package prerequisite: Requires the solution package to be already uploaded to Solutions Management in Orchestrator.
- Folder structure: Creates or uses deployment folders to organize solution files within Orchestrator.
- Configuration support: Supports custom configuration files for environment-specific settings.
- Deployment management: Can create new deployments or update existing ones based on the deployment name.
- CLI compatibility: This task uses the UiPath CLI internally and requires proper CLI installation on the build agent.
- Minimum CLI version: Requires UiPath CLI version 25.10 or higher for full compatibility.
- Environment targeting: Deployment folders allow targeting specific environments (dev, test, prod).
Pipeline examples
Basic solution deployment
- task: UiPathSolutionDeploy@6 displayName: 'Deploy Solution' inputs: orchestratorConnection: 'UiPath-Orchestrator-Connection' packageName: 'MySolution' packageVersion: '1.0.$(Build.BuildId)' deploymentName: 'MySolution-Deployment' deploymentFolderName: 'Production' traceLevel: 'Information'- task: UiPathSolutionDeploy@6 displayName: 'Deploy Solution' inputs: orchestratorConnection: 'UiPath-Orchestrator-Connection' packageName: 'MySolution' packageVersion: '1.0.$(Build.BuildId)' deploymentName: 'MySolution-Deployment' deploymentFolderName: 'Production' traceLevel: 'Information'With Orchestrator connection and custom configuration
- task: UiPathSolutionDeploy@6 displayName: 'Deploy Solution with Custom Config' inputs: orchestratorConnection: 'Production-Orchestrator' packageName: 'MyBusinessSolution' packageVersion: '2.1.$(Build.BuildNumber)' deploymentName: 'BusinessSolution-Prod-Deploy' deploymentParentFolder: 'Production' deploymentFolderName: 'BusinessApps' configPath: '$(Build.SourcesDirectory)/configs/production.config' traceLevel: 'Verbose'- task: UiPathSolutionDeploy@6 displayName: 'Deploy Solution with Custom Config' inputs: orchestratorConnection: 'Production-Orchestrator' packageName: 'MyBusinessSolution' packageVersion: '2.1.$(Build.BuildNumber)' deploymentName: 'BusinessSolution-Prod-Deploy' deploymentParentFolder: 'Production' deploymentFolderName: 'BusinessApps' configPath: '$(Build.SourcesDirectory)/configs/production.config' traceLevel: 'Verbose'Complete pipeline: upload and deploy
variables: solutionName: 'MyBusinessSolution' solutionVersion: '1.$(Date:yyyy).$(DayOfYear)$(Rev:.r)' environmentName: 'Production'steps:- task: UiPathSolutionUploadPackage@6 displayName: 'Upload Solution Package' inputs: orchestratorConnection: 'Production-Orchestrator' solutionPackagePath: '$(Build.ArtifactStagingDirectory)/Packages/$(solutionName).$(solutionVersion).zip' traceLevel: 'Information'- task: UiPathSolutionDeploy@6 displayName: 'Deploy Solution to $(environmentName)' inputs: orchestratorConnection: 'Production-Orchestrator' packageName: '$(solutionName)' packageVersion: '$(solutionVersion)' deploymentName: '$(solutionName)-$(environmentName)-$(Build.BuildNumber)' deploymentParentFolder: '$(environmentName)' deploymentFolderName: 'BusinessProcesses' configPath: '$(Build.SourcesDirectory)/configs/$(environmentName).config' traceLevel: 'Information'- script: echo "Solution $(solutionName) v$(solutionVersion) deployed to $(environmentName)" displayName: 'Deployment Summary'variables: solutionName: 'MyBusinessSolution' solutionVersion: '1.$(Date:yyyy).$(DayOfYear)$(Rev:.r)' environmentName: 'Production'steps:- task: UiPathSolutionUploadPackage@6 displayName: 'Upload Solution Package' inputs: orchestratorConnection: 'Production-Orchestrator' solutionPackagePath: '$(Build.ArtifactStagingDirectory)/Packages/$(solutionName).$(solutionVersion).zip' traceLevel: 'Information'- task: UiPathSolutionDeploy@6 displayName: 'Deploy Solution to $(environmentName)' inputs: orchestratorConnection: 'Production-Orchestrator' packageName: '$(solutionName)' packageVersion: '$(solutionVersion)' deploymentName: '$(solutionName)-$(environmentName)-$(Build.BuildNumber)' deploymentParentFolder: '$(environmentName)' deploymentFolderName: 'BusinessProcesses' configPath: '$(Build.SourcesDirectory)/configs/$(environmentName).config' traceLevel: 'Information'- script: echo "Solution $(solutionName) v$(solutionVersion) deployed to $(environmentName)" displayName: 'Deployment Summary'