Make sure that your network allows access to the following NuGet package feed:
Release date: 14 February 2023
- For more flexibility, you can now replace the default version of the command-line interface (CLI) that comes with the Azure DevOps extension, with whatever version of the CLI that you want, as long as it's compatible. To replace the default version of the CLI, use the UiPath InstallPlatform task and select the desired version from the dropdown list. Learn how to use the UiPath InstallPlatform task here.
With this release, the default CLI version that comes with it is 21.10, but you can now choose to download a different version of the CLI, by using the UiPath InstallPlatform task This offers the possibility to pack Windows and Cross-platform projects.
The UiPath InstallPlatform 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.
All the errors that the Packager throws at compilation can now be viewed and investigated from the console error logs.
Windows projects deployed using the Azure DevOps extension now successfully execute in Orchestrator.
The basic authentication header was removed from Orchestrator requests.
An error occurred when publishing a Windows package through UiPath Deploy due to an output type discovery issue within the project.json file.
Packages were deployed as libraries in Orchestrator, even if the input JSON file explicitly specified the
Process. This behavior is now fixed.
Fixed a bug that allowed the Workflow Analyzer to analyze YAML files.
Release date: 15 November 2022
Due to a restriction to packaging, a Windows project failed with the following error: "Failed to run the command. Sytsem.ID.FileNotFoundException: Could not find file
Windows.PlatformManifest.txt". This issue is fixed now.
Release date: 17 October 2022
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.
Release date: 5 September 2022
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.
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
valuearguments, with one exception. When you create new input arguments at the Test Set level, you will still need to provide the
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.
Release date: 13 April 2022
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:
Release date: 8 February 2022
When you configure a UiPath Test job, you can view INFO level logs by attaching Robot Logs.
For more information, see Configuring UiPath Test.
Service connection configured with an external application did not authenticate properly. This issue has been fixed by addressing an Identity URL misconfiguration.
Packaging projects with custom libraries resulted in an error due an Orchestrator authentication error.
An authentication issue prevented package deployment through Orchestrator instances deployed in Azure Marketplace, resulting in an error. This issue has been addressed with a new field in the External Application configuration.
For more information, see Service Connection Configuration for External Applications.
Test sets executing a large number of test cases (e.g., 1400) resulted in an error. This issue has been addressed by delaying concurrent Orchestrator API calls.
Release date: 7 December 2021
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.
Release date: 11 November 2021
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.
Release date: 8 November 2021
Case formatting for project names was affected by an UiPath Pack issue.
Packing libraries with Data Service objects resulted in failure. This issue has been addressed.
Packages with single entry points are not appended to process names, unless there are multiple entry points. As a result, jobs didn’t load. This issue has been addressed.
Deploying packages through an external application configured with Orchestrator version 2021.4 resulted in an error.
Release date: 11 October 2021
Your Orchestrator on-premises instance can now be configured as a service connection, making way for authentication with Orchestrator through external apps.
Now you can use Testing Robots to test your workflows in non-production environments. This is intended for non-production environments only. You can select this option when you configure the UiPath Run Job.
Test results now include a link for test case logs that show detailed execution events.
We have listed the official feeds that we use for the UiPath NuGet package. To view the list, see UiPath Deploy.
Test case running data variations now have a count added to each test case title, so you can distinguish between results.
Release date: 3 September 2021
Deploying test project packages to Orchestrator resulted in error as they can have multiple entry points. This issue has been addressed by ignoring entry points for packages published from a Testing project.
Release date: 1 September 2021
This update brings changes to the Orchestrator authentication, new test set configurations, and bugfixes.
- Authentication with Orchestrator is now possible through external apps. You can configure Orchestrator as a new service connection.
- You can configure the UiPath Pack task used for publishing packages in Orchestrator, to report workflow validation errors. This additional configuration allows you to check your project for Workflow Analyzer violations.
- Now you can parameterize your test cases at runtime by defining arguments at the test set level. You can use this feature to reconfigure existing test cases by overriding the default argument value, instead of creating new ones.
- Test results now show assertion details.
- Libraries within Object Repository that were published through the plugin did not show Object Repository details in Studio.
- Using the UiPath Deploy task to create a process that was already existent in Orchestrator resulted in error.
Release date: 3 August 2021
This update adds additional information to the testing items and fixes a couple of bugs.
- Folders with a dedicated package feed are now supported for package deployment.
- Test results now contain assertion details and outcomes, and arguments such as device information to help you identify executed test cases.
- Links to the Orchestrator test set results are now available as part of the UiPath Test job output.
- Now you can define entry points (XAML files) when configuring a process. This is helpful for packages with multiple entry points activated.
- When you run a job, you can select whether it is going to be executed through production or non-production robots.
- Now, you can provide a description for Assets ca within the CSV file.
- The asset descriptions were not properly displayed due to a character encoding issue.
- Packaging libraries that included namespaces with periods through the UiPath Pack task failed.
Release date: 23 March 2021
This update fixes a couple of bugs.
- Packaging Orchestrator projects version 2018.x did not work with the UiPath Integration for Azure DevOps version 2.3. The issue has been fixed using UiPath Pack with Studio version 2018.x.
- Executing tests within Orchestrator processes did not work whenever they were uploaded via the UiPath Deploy task and then ran through the UiPath Run Tests task. This issue was caused by a duplicate package version in Orchestrator.
- Executing UiPath Manage Assets task on non-Windows build agents did not result in a proper error message. Now, when the UiPath Manage Assets task runs on a non-Windows build agent, the information is logged within the command-line.
Release date: 11 March 2021
This update provides compatibility with our latest UiPath Cloud Orchestrator version. If you are using a cloud-hosted UiPath Orchestrator, make sure that you update your UiPath Azure DevOps extension.
- Our tasks are now all localizable, supporting the following languages: German, English, Spanish, French, Portuguese, Russian, Turkish, Korean, Chinese, Japanese.
- For changing your display language in Azure DevOps, see Set user preferences.
- If your local language is not supported, our plugin will fall back to English.
When packing libraries, we now output more logging information about the compiling process. Also, packing a library will fail if the library compilation fails.
- We fixed an issue were packing a process with an entry point XAML file that contains In/Out argument would not create the In/Out arguments in the generated package, resulting in the arguments not being available in Orchestrator.
- We fixed an issue that resulted in packing incorrectly a library when the task is run on a Windows machine with FIPS enabled.
- We fixed an issue where the Test task would fail if used in a Release pipeline.
Release date: 8 December 2020
Run job executions as part of a new task called Run Job.
Manage assets as part of a new task called UiPathAssets. You can either deploy using an upsert operation, or delete assets.
Logging is now improved with clear-cut error messages that provide context and call-to-action.
- Custom non-activity packages are deployed in the libraries feed when using the Deploy task
- The UiPath Pack task compiles expressions and VBA activities.
- Extension configuration includes non-Latin characters.
Updated 22 days ago