cicd-integrations
2024.10
true
- Overview
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- About UiPath CLI tasks
- 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
Last updated May 23, 2025
UiPath Pack
The UiPathPack task enables you to package an existing UiPath project into a NuGet package.
Use the following table to configure the UiPath Pack inputs.
| Argument | Description |
|---|---|
| Display name (Required) | Enter a name for your task. |
| Choose versioning method (Required) | You can select an automatically generated version, use the project version, or define a new version. For more information, see Package Versions. |
| Version (Required) | Available only on modern folders alongside a dynamic allocation strategy. Specifying the package version provides the possibility
of tracking the built packages and their source versioning more efficiently. For example, the Microsoft assembly pattern can
be utilized to build the NuGet package version: [Major].[Minor].[BuildNumber].[RevisionNumber].
The available options are:
|
| Project(s) Path (Required) | Select the location of the project that is going to be packaged. It can be a direct path to a project.json file or a directory with one or multiple projects. In the latter case, each level one project is packaged individually. |
| Choose output type (Required only for manual versioning) | Set a project type for the project that is going to be packaged. If you set None, the project type is going to be extracted from the project's JSON file.The following project types are supported: 'Process',
'Library', 'Tests', 'Objects', 'None'.
|
| 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. |
| Output Path (Required) | Set a folder path where the package is going to be placed. |
| Run workflows analysis | Select this option to run workflow analysis rules on your automation project (e.g., Fail jobs in case of errors). By default, this option is not activated. For more information, see Application Testing Workflow Analyzer Rules. |
| Trace Level | Select the logging level from the dropdown list. |
You can preview a fully parsed YAML document for the UiPath Pack.
- task: UiPathPack@2
inputs:
#versionType: AutoVersion # Options: AutoVersion, CurrentVersion, ManualVersion
#version: '1.0.0' # Required when versionType == ManualVersion
#projectJsonPath: '$(Build.SourcesDirectory)\MyFirstProcess'
#outputPath: '$(Build.ArtifactStagingDirectory)\Packages\MyFirstProcess'
#outputType: 'None' # Options: Process, Library, Tests, Objects, None
#runWorkflowAnalysis: 'False'
#orchestratorConnection: 'service-connection-name' # Service connection to UiPath Orchestrator,
#traceLevel: 'None' # Options: Critical, Error, Warning, Information, Verbose, None- task: UiPathPack@2
inputs:
#versionType: AutoVersion # Options: AutoVersion, CurrentVersion, ManualVersion
#version: '1.0.0' # Required when versionType == ManualVersion
#projectJsonPath: '$(Build.SourcesDirectory)\MyFirstProcess'
#outputPath: '$(Build.ArtifactStagingDirectory)\Packages\MyFirstProcess'
#outputType: 'None' # Options: Process, Library, Tests, Objects, None
#runWorkflowAnalysis: 'False'
#orchestratorConnection: 'service-connection-name' # Service connection to UiPath Orchestrator,
#traceLevel: 'None' # Options: Critical, Error, Warning, Information, Verbose, None
