UiPath Integration (Public Preview)
The UiPath Integration extension provides a task to support build and release pipelines for UiPath projects. You can use this task to:
Starts from the project sources taken from source control. The result is a NuGet package ready to be shipped to Orchestrator. It provides control over the following:
By using the Chose the versioning method field you can decide whether the NuGet package version should be pseudo-randomly generated by the task or provide a specific one. Auto-generating the version works just as Studio does the versioning when publishing a package. Specifying the package version provides the possibility of tracking more efficiently the built packages and their source versioning. For example, the Microsoft assembly pattern can be utilized to build the NuGet package version: [Major].[Minor].[BuildNumber].[RevisionNumber]. As a best practice, these fields should be stored as variables.
UiPath Studio Setup On Build Agent Machine
The pack functionality wraps around the UiRobot.exe -pack command, so UiPath Studio needs to be installed on the build agent. The following scenarios exist: UiPath Studio is installed on the build agent or it is not. In case we’re facing a build agent that doesn’t have UiPath installed, you can configure the task to do so by following one of these two options:
In some cases, UiPath Studio might be already installed on the build agent machine and you want to make sure that a certain version is utilized to do the packaging. To have control over these situations, you can use the Uninstall options feature. It provides the following options:
Project JSON Path
Most of the times the project.json file is located in the root folder of the UiPath process. In the situations when it’s not there you have the possibility to mention it in the Project json path field.
By default this is set to $(build.artifactstagingdirectory). In case you want the NuGet package to be stored in another location this field can be configured as such.
After having the NuGet package (or packages) built they can be published to Orchestrator by utilizing the Deploy function. It retrieves all nuget packages from the specified location, Package path, and publishes them into Orchestrator using its API. The API calls use Bearer authentication, and therefore you need to provide your Tenant, Username, and Password. Strong recommendation: don’t hard code username and password fields, use variables!
Deploy function requires NuGet to be installed on the agent machine. The recommended version is 2.8 or newer.