cicd-integrations
2024.10
true
- Overview
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- About UiPath CLI tasks
- Packing projects into a package
- Analyzing a project
- Deploying a package to Orchestrator
- Running a job inside Orchestrator
- Testing a package or running a test set
- Testing multiple packages
- Deploying assets to Orchestrator
- Deleting assets from Orchestrator
- Running tasks using JSON configuration
- Restoring automation dependencies
- Troubleshooting UiPath CLI
- Azure DevOps extension
- Jenkins plugin
CI/CD integrations user guide
Last updated May 5, 2025
Running Jenkins jobs
Before running a job, make sure you meet the following requirements:
- All paths specified should be local to the current workspace. You can use environment variables in paths, though you should make sure that they result in paths that are local to the workspace.
- To deploy packages or run tests, make sure that the authenticated user has the Folders View (or OrganizationUnits View) and (20.4+ only) Background Tasks View permissions.
- To package libraries, when connected to an Orchestrator instance, make sure that the authenticated user has the Libraries View permission.
To know more about the specific tasks you can execute through the Jenkins plugin, consider reviewing the following topics:
