cicd-integrations
2025.10
true
- Overview
- About CI/CD pipelines
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- 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 Nov 12, 2025
About CI/CD Pipelines
What are CI/CD pipelines
Continuous Integration and Continuous Delivery (CI/CD) pipelines automate how automations are built, tested, versioned, and promoted between environments such as Development, Test, and Production. They ensure repeatable delivery, consistent governance, and clear traceability across the automation lifecycle.
Why use CI/CD for automations
- Repeatability: Every build and deployment follows the same tested process.
- Governance: Automated validations and approvals enforce organizational standards.
- Auditability: All changes, versions, and promotions are traceable.
- Scalability: The same DevOps practices used for software delivery apply to automations.
How UiPath CLI fits in
The UiPath Command Line Interface (CLI) is the foundation for enabling CI/CD with UiPath. It provides a unified way to:
- Package automation assets such as Processes, Libraries, Tests, and Solutions.
- Validate projects with Workflow Analyzer and governance policies.
- Publish and deploy artifacts to Orchestrator or Automation Cloud.
- Activate deployed Solutions with environment-specific configurations.
Solutions in CI/CD
CI/CD pipelines support Solutions, which group multiple automations, assets, and configurations into a single deployable unit. Solutions follow the same CI/CD flow as individual projects — packaged once, validated, deployed, and activated in target environments.
Typical automation lifecycle in CI/CD
- Checkout source code from version control.
- Validate and build automation assets.
- Package and publish to an internal or external feed.
- Deploy to the target environment (e.g., Test, UAT, Production).
- Activate the deployment (for Solutions) using environment-specific settings.
Next steps
- Continue to About UiPath CLI to learn about CLI installation, authentication, and usage.
- Explore Working with Solutions to see how multi-project automations fit into the pipeline.
