4.0.327.v39580c233fd7

💥 Breaking changes

• plugin versioning and tagging changes

🚀 New features and improvements

• upgrade the prepackaged CLI to the newly released UiPath.CLI.Windows.24.10.9050.17872 which requires .NET 8
• add in UiPathInstallPlatform picklist UiPath.CLI.Windows.24.10.9050.17872 and UiPath.CLI.24.10.9050.17872
• expose governanceFilePath for analyze in UiPathPack to enable passing of a governance policy json file with rules for the workflow analyzer
• expose processNames argument for configuration file path with custom names for multiple processes in UiPathDeploy
• expose ignoreLibraryDeployConflict for UiPathDeploy to avoid failing the task in case the deployment is duplicated

📦 Dependency updates

• bump jenkins version from 2.387.3 to 2.414.3
• bump org.jenkins-ci.plugins:junit version from 1265.v65b_14fa_f12f0 to 1304.vc85a_b_ca_96613
• bump org.yaml:snakeyaml from 1.33 to 2.3
• bump org.jenkins-ci.modules:instance-identity from 185.v303dc7c645f9 to 201.vd2a_b_5a_468a_a_6

uipath-automation-package-3.2

What's New

UiPath.CLI 23.10.8894.39673 patch

Added in UiPathInstallPlatform picklist UiPath.CLI.Windows.23.10.8894.39673 and UiPath.CLI.23.10.8894.39673 patches.
The default version will be UiPath.CLI.Windows.23.10.8894.39673 (latest patch).
The prepackaged version will be UiPath.CLI.Windows.23.10.8894.39673 (latest patch).

Add release notes

You can add release notes when packaging an automation project or a test automation by setting the releaseNotes argument.

Disable built-in feeds

You can disable the built-in feeds when packaging an automation project or a test automation by setting the disableBuiltInNugetFeeds argument.
You can specify your custom feeds in a nuget.config file. Here is documentation with more guidance.

Dependency updates

Update minimum jenkins server version to 2.387.3.
Update dependency plain-credentials to 179.vc5cb_98f6db_38.
Update dependency credentials to 1319.v7eb_51b_3a_c97b_.
Update dependency junit to 1265.v65b_14fa_f12f0.
Update dependency structs to 325.vcb_307d2a_2782.
Update dependency caffeine-api to 3.1.8-133.v17b_1ff2e0599.
Update dependency instance-identity to 185.v303dc7c645f9.

uipath-automation-package-3.1

What's New

UiPath.CLI 23.10

Added in UiPathInstallPlatform picklist UiPath.CLI.Windows.23.10 and UiPath.CLI.23.10.
The default version will be UiPath.CLI.Windows.23.10.
The prepackaged version will be UiPath.CLI.Windows.23.10.

Telemetry

By default telemetry data will be sent.
PII data is hashed.
You can disable telemetry by setting UIPATH_EXTENSIONS_CLI_TELEMETRY_ENABLED environment variable on the agent executing the tasks to False.
If the agent is isolated from the internet (onPrem), telemetry will not be sent and the execution of the tasks will continue without errors.

Library split

The same functionality Studio has.
When packing a library you can split the output into 2 nupkg files by setting splitOutput=true, which is an optional parameter.
By default, libraries will not be splited in order to maintain backwards compatibility.

Set optional package metadata

On Pack/RunTests from a project.json, you can optionally specify: RepositoryUrl, RepositoryCommit, RepositoryBranch, RepositoryType, ProjectUrl parameters. These will be written in the created nupkg files.

Bug Fixes

WORKSPACE environment variable bug

In certain scenarios and certain pipeline types (multibranch, freestyle or pipeline), some environment variables were not correctly fetched. Due to this, WORKSPACE environment being an important value in the jenkins context, the pipeline failed with errors.

UiPath.CLI download flow

Jenkins was not able to download the selected uipcli from the picklist, other than the default prepackaged version.

Wrong identityUrl

Jenkins plugin passed a wrong identityUrl to uipcli in some scenarios.

uipath-automation-package-3.0

What's New

Jenkins Long Term Support
With this release, the Jenkins Plugin supports the latest Jenkins Long Term Support (LTS) version of Jenkins: 2.361.2 LTS

Install Platform task

The more the merrier! A new task has been added to the Jenkins plugin. The UiPath Install Platform task supports you in finding and downloading the right version of the command-line-interface (CLI) that you want. Being able to download the right version of the CLI makes sure that the Jenkins plugin is compatible with your environment, and that you can pack Windows and Cross-platform projects using later versions of the CLI.

The default CLI version that comes with this version of the plugin is 21.10, but you can choose to download a later version.

Overall, the UiPath Install Platform task allows you to:

Download, and implement a different version of the CLI, using the Choose a CLI version dropdown list.
Implement a different version of the CLI, by manually downloading the CLI NUPKG file, placing it on your build agent, and specifying that path in the Path to CLI's nupkg field. This scenario applies for cases when your pipeline can't access the UiPath Public Feed to download the CLI.
Learn how to use the UiPath Install Platform task here.

Improvements

All the errors that the Packager throws at compilation can now be viewed and investigated from the console error logs.
The Jenkins plugin is trusted and verified in the CloudBees marketplace.

Bug fixes

Fixed a bug that caused the manifest.json files to be missing from the UiPath.CLI NuGet package.
Jenkins tasks failed if the Orchestrator folder name contained the & symbol. Now, Orchestrator folder names with the & symbol can be passed as a parameter with the tasks.
The Workflow Analyzer failed with Jenkins if the analyzed package has additional files.
The publishing of test results failed with the following error: Receiver class com.uipath.uipathpackage.UiPathTest does not define or inherit an implementation of the resolved method 'abstract boolean isSkipOldReports()' of interface hudson.tasks.junit.JUnitTask.
Fixed a bug that allowed the Workflow Analyzer to analyze YAML files.
Packages were deployed as libraries in Orchestrator, even if the inputted JSON file explicitly specified the outputType parameter as Process.

uipath-automation-package-2.11

What's New

In this release we ironed out a few bugs.

Bug Fixes

An error occurred when publishing a Windows package through UiPath Deploy due to an output type discovery issue within the project.json file. This issue has been addressed.

uipath-automation-package-2.10

Bug Fixes

• The package version update using UiPath Deploy failed for Orchestrator version 2021.10. This issue has been addressed.
• Deployed packages were not visible using UiPath Deploy, when Orchestrator was connected through the External Application method.
• The dropdown list for the Strategy parameter in UiPath Run Job did not work correctly.

Improvements

• You can now skip process creation through UiPath Deploy by selecting the Automatically create a process parameter, when you build your pipeline.

• The Entry Points argument from UiPath Deploy has been renamed to Entry Point Path(s) to make it more suggestive in scenarios where the entry point XAML file is nested in folders. Additionally, a tooltip has been added to indicate the file path.
  See UiPath Deploy (Entry Point Path(s).

• The following changes have been made to assets uploaded as CSV files through UiPath Manage Assets:

  • CSV file containing commas now support quotes within values.
  • Comments are no longer supported.
  • JSON values are now supported.

  For more information and examples, see UiPath Manage Assets Configuration (Asset CSV File).

• Input parameters specified through a JSON file for UiPath Test will now require only name and value arguments, with one exception. When you create new input arguments at the Test Set level, you will still need to provide the type argument.

uipath-automation-package-2.9.2

What's New

In this release we ironed out a few bugs.

Improvements

The UiPath Deploy works by creating a process for a newly published package and patching (updating to a new version) any existing process. These actions could generate validation errors if an entry point is not specified within the process metadata.

To address this issue, the actions taken by the UiPath Deploy task have been changed as follows:

• If a process exists and does not contain an entry point specified by the UiPath Deploy task, then it is going to be patched.
• If there is no process with the entry point specified by the UiPath Deploy task, then a new process is created using the following append structure: MyPackageName_Entrypoint.xaml.

uipath-automation-package-2.9.1

What's New

In this release we ironed out a few bugs.

Improvements

• Service connection configured with an external application did not authenticate properly. This issue has been fixed by addressing an Identity URL misconfiguration.
• An error occurred while packaging a project through the UiPath Pack task due to missing Orchestrator libraries

uipath-automation-package-2.9.0

What's New

In this release we ironed out a few bugs.

Improvements

• Authentication for Orchestrator deployments in Microsoft Azure Marketplace failed due to an Identity Server issue. This issue has been addressed by adding a new field to the External Application authentication method, where you can add the Identity Server URL.

uipath-automation-package-2.8.1

What's New

In this release we ironed out a few bugs.

Improvements

• UiPath Deploy did not upload packages due to an entry point process name conflict.

• Deploying a package through Orchestrator at the folder level resulted in error. This issue was caused by the usage of a deprecated API package feed for Orchestrator versions older than 21.4.