- Get started
- Best practices
- Capabilities
- Skills
- CLI
- Examples
- Examples overview
- Recipe: build an agent
- Recipe: automate with RPA
- Recipe: enter data into a web app
- Recipe: extract data from a desktop app
- Recipe: refactor and test a workflow
- Recipe: a queue-based process with REFramework
- Recipe: build a Maestro Flow
- Recipe: coded app and API workflow
- Recipe: verify a release with Test Manager
- Recipe: extract data from documents with IXP
- Advanced
- CI/CD and automation
- Governance and trust
- Help
Once you build locally, you can run the same uip CLI in a pipeline to publish and run automations automatically — without the interactive browser login. This guide outlines the shape of a CI/CD setup.
Prerequisites
- A CI/CD system such as GitHub Actions or Azure DevOps.
- UiPath credentials suitable for non-interactive authentication, stored as pipeline secrets.
Set up a pipeline job
-
Store your UiPath credentials as secrets in your CI/CD system, never in the repository.
-
Install the CLI in the pipeline job:
npm install -g @uipath/clinpm install -g @uipath/cli -
Authenticate non-interactively using your stored secrets. Run
uip login --helpto see the options for headless authentication, since interactive browser login is not available in CI. -
Run your publish or job command as the next pipeline step, referencing the project to publish or the job to start.
-
Check the command's exit code so the pipeline fails when the UiPath step fails.
Result: the pipeline authenticates and runs your UiPath commands automatically on each trigger.
The exact non-interactive authentication options and publish commands are defined by your CLI version. See the UiPath CLI documentation and uip login --help for the authoritative flags.