cicd-integrations
2022.10
false
- Overview
- UiPath CLI
- Azure DevOps extension
- Jenkins plugin
CI/CD integrations user guide
Last updated Apr 28, 2025
Executing Azure DevOps tasks
Your pipeline is composed of different stages, that in turn, can be broken down into jobs. For each job, you can configure the steps to include the UiPath tasks, included with the UiPath Integration for Azure DevOps.
Important: Starting with April 2023, and 2023.4, new executions will be blocked in classic folders. For tasks that include a classic folder in their configuration, a
Folder not found message is displayed, and the task is not performed. Learn more about classic folder removal here.
To know more about the specific tasks you can execute through the Azure DevOps extensions, consider reviewing the following topics:
The Azure DevOps Extension comes with a built-in CLI (Command-Line interface ) that is specific to UiPath.
When you run over the build agent, the UiPath CLI communicates with Orchestrator and allows you to execute your job tasks.
By default, UiPath CLI is prepackaged within the AzureDevOps extension, and it is stored inside the
Agent.ToolsDirectory (Azure cache) when executing it for the first time.
When running a job task over the build agent, the system checks for UiPath CLI that should be inside the
Agent.ToolsDirectory, in order to finish the execution.
If UiPath CLI is not found inside the
Agent.ToolsDirectory (Azure cache), the system automatically downloads it from the NuGet public feed. A requirement for this is that the NuGet
public feed is not blocked by a firewall, and can be accessed from your build agent.
If you are not able to open up your firewall from your build agent, you can manually download UiPath CLI (corresponding to
the build version used for your current plugin), and manually place it inside the
Agent.ToolsDirectory, using the Install Platform task.
