CI/CD integrations release notes

Last updated Nov 12, 2025

6.0.332.v34005c6b_9c7a_

Release date: 6 November 2025

What's new

Solutions support

Jenkins plugin v6.0 introduces full support for UiPath Solutions, enabling packaging, deployment, and configuration management directly within Jenkins pipelines.

New build steps:

UiPath Solution Pack - Pack Solutions into distributable artifacts (solution pack)
UiPath Solution Upload Package - Upload Solution package to Automation Cloud (solution upload-package)
UiPath Solution Delete Package - Remove Solution package (solution delete-package)
UiPath Solution Download Package - Download Solution package (solution download-package)
UiPath Solution Download Config - Download Solution configuration (solution download-config)
UiPath Solution Deploy - Deploy Solution package to target environment (solution deploy)
UiPath Solution Activate Deployment - Activate Solution deployment with environment-specific settings (solution deploy-activate)
UiPath Solution Uninstall Deployment - Uninstall Solution deployment from environment (solution deploy-uninstall)

CLI integration updates The plugin now installs UiPath CLI 25.10 by default and supports all three CLI packages:

UiPath.CLI.Windows
UiPath.CLI.Linux
UiPath.CLI.Windows.Legacy

Breaking change: Older CLI versions (23.x / 24.x) are no longer automatically installed.

Enhanced build step capabilities

Updated all existing build steps to support CLI 25.10 features.
Improved error handling and logging in Jenkins console output.
Better support for declarative and scripted pipeline syntax.

Requirements

Requires UiPath CLI 25.10 or later.
Compatible with Jenkins 2.414.3 or later.
Compatible with Automation Cloud Orchestrator.
Solutions deployment is currently supported only in Automation Cloud.

Migration notes

When upgrading to plugin v6.0:

Update Jenkins pipelines to use CLI version 25.10 in the UiPathInstallPlatform step.
Update CLI package references in any custom build steps.
Review and test all pipeline definitions before production deployment.
Ensure Jenkins server and agents have .NET 8 runtime installed.

Dependency updates

Updated to support UiPath CLI 25.10 (requires .NET 8).
Enhanced compatibility with the latest Jenkins LTS versions.

Breaking changes

Important:

Jenkins Plugin v6.0 introduces significant changes to CLI version management. Review these breaking changes carefully before upgrading.

CLI version availability

What changed: The CLI version dropdown in UiPathInstallPlatform now lists only UiPath CLI 25.10 and later versions. Older CLI versions (23.x, 24.x) are no longer available for automatic installation through the plugin.

Action required:

Update all Jenkins pipeline definitions to reference CLI version 25.10 or later.
Replace any references to older CLI versions in your pipelines.

CLI flavor separation

What changed: UiPath CLI is now distributed as three separate packages:

UiPath.CLI.Windows - for Cross-platform and Windows (non-legacy) projects
UiPath.CLI.Linux - for Cross-platform projects on Linux
UiPath.CLI.Windows.Legacy - exclusively for Windows - Legacy projects only

Why this matters:

Windows - Legacy projects can no longer be packaged using UiPath.CLI.Windows.
You must use UiPath.CLI.Windows.Legacy for all Windows - Legacy projects.

Action required:

Identify the project types in your repository.
Update your pipeline to install the appropriate CLI flavor(s).

Mixed project types in the same repository

What changed: If your repository contains both Windows - Legacy projects and other project types (Cross-platform or Windows non-legacy), you must:

Install multiple CLI flavors in your pipeline:
- UiPath.CLI.Windows (for Cross-platform and Windows projects)
- UiPath.CLI.Windows.Legacy (for Windows - Legacy projects)
Organize your build stages to process each project type with the correct CLI.

Example pipeline approach:

stage('Install CLI for Modern Projects') {    steps {        UiPathInstallPlatform(            version: 'Windows.25.10.0-20251104-11',  // UiPath.CLI.Windows        )    }}stage('Build Modern Projects') {    steps {        // Pack cross-platform and Windows (non-legacy) projects    }}stage('Install CLI for Legacy Projects') {    steps {        UiPathInstallPlatform(            version: 'Windows.Legacy.25.10.9424.14050',  // UiPath.CLI.Windows.Legacy        )    }}stage('Build Legacy Projects') {    steps {        // Pack Windows - Legacy projects    }}stage('Install CLI for Modern Projects') {    steps {        UiPathInstallPlatform(            version: 'Windows.25.10.0-20251104-11',  // UiPath.CLI.Windows        )    }}stage('Build Modern Projects') {    steps {        // Pack cross-platform and Windows (non-legacy) projects    }}stage('Install CLI for Legacy Projects') {    steps {        UiPathInstallPlatform(            version: 'Windows.Legacy.25.10.9424.14050',  // UiPath.CLI.Windows.Legacy        )    }}stage('Build Legacy Projects') {    steps {        // Pack Windows - Legacy projects    }}

Important notes:

There is no automatic detection of project types. You must know which projects are Windows - Legacy.
Consider organizing projects by type in separate folders for easier pipeline management.
Refer to UiPath Install Platform (Jenkins) for detailed guidance.

.NET Runtime requirement

What changed:

All UiPath CLI 25.10 packages require .NET 8 Runtime. Previous versions used .NET 6.

Action required:

Ensure all Jenkins agents have .NET Desktop Runtime 8 (Windows) or .NET Runtime 8 (Linux) installed.
Remove .NET 6 runtime dependencies from agent setup documentation.