cicd-integrations
2023.4
false
- Overview
- UiPath CLI
- Azure DevOps extension
- Jenkins plugin
CI/CD integrations user guide
Last updated Apr 28, 2025
UiPath Deploy
The UiPathDeploy task lets you deploy a UiPath NuGet package onto UiPath Orchestrator.
Important:
Make sure that your network allows access to the following NuGet package feed:
- https://api.nuget.org/v3/index.json
- https://uipath.pkgs.visualstudio.com/_packaging/nuget-packages/nuget/v3/index.json
- https://uipath.pkgs.visualstudio.com/Public.Feeds/_packaging/UiPath-Internal/nuget/v3/index.json
- https://www.myget.org/F/workflow
- http://www.myget.org/F/uipath
- https://www.myget.org/F/uipath-dev/api/v3/index.json
Use the following table to configure the UiPath Deploy inputs.
| Argument | Description |
|---|---|
| Display name (Required) | Enter a name for your task. |
| Orchestrator connection (Required) | Configure the service connection to access UiPath Orchestrator services. You can configure a connection only for this step or use an existing global connection. For more information, see Configuring UiPath Orchestrator service connection. |
| Package(s) (Required) | Define the feed for your UiPath NuGet packages. |
| Automatically create process | Select this option if you want to deploy a package without creating a process. The option is selected by default.If selected, you need to configure the Entry Point Path parameter. |
| Orchestrator folder (Required) | Specify the folder where the process is being deployed. For classic folders (deprecated), you can use specific robot names.
For modern folders, you can use specific user and machine names.
To input subfolders make sure to input both the parent folder name and the name of the subfolder. For instance, use
AccountingTeam\TeamJohn.
|
| Environment | (Optional) If you use classic folders (deprecated), you need to define the environment where the packages are going to be
deployed. You can use this field to create or update packages.You can use the following example to add your environments to
this field, separated by a comma: testingEnvironment,productionEnvironment.
|
| Entry Point Path(s) (Required) | Specify entry point paths to create or update a process. The entry point path specifies the file path starting from the root
of the project.Before configuring the entry point paths, consider the following: Entry points are available for Orchestrator
version 21.4 or higher (e.g. 21.4.UiPathDeploy.entryPoints). For Orchestrator versions lower than 21.4, you need to enter any value, as the field must not remain empty. The default
entry point is set to Main.xaml. Multiple entrypoints can be specified as 'Main.xaml, EntryPoint2.xaml '. For classic folders (deprecated) you can specify
only one entry point for each environment. For nested folders you need to specify the file path, as follows:Folder01/Folder02/Main.xaml or Folder01/Folder02/Entrypoint.xamlFor more information, see Orchestrator Entry Points.
|
| Trace Level | Select the logging level from the dropdown list. |
You can preview a fully parsed YAML document for the UiPath Deploy.
- task: UiPathDeploy@2
inputs:
#orchestratorConnection: # Service connection to UiPath Orchestrator
#packagesPath: '$(Build.ArtifactStagingDirectory)\Packages\ITAutomationProcess'
#folderName: 'ITAutomation'
#environments: 'AutomationRobots' # Optional,
#traceLevel: 'None' # Options: Critical, Error, Warning, Information, Verbose, None- task: UiPathDeploy@2
inputs:
#orchestratorConnection: # Service connection to UiPath Orchestrator
#packagesPath: '$(Build.ArtifactStagingDirectory)\Packages\ITAutomationProcess'
#folderName: 'ITAutomation'
#environments: 'AutomationRobots' # Optional,
#traceLevel: 'None' # Options: Critical, Error, Warning, Information, Verbose, None
