UiPath RPA

Build UiPath packages from Git and deploy them to Orchestrator folders with automated environment promotion across Dev, Test, and Production — with instant rollback support.

Prerequisites

• UiPath Orchestrator instance accessible (Cloud or On-Premise)Git repository with UiPath projects registered in Opsera Tool Registry

• UiPath tool registered with Org Name, Auth Type, Client ID, and Client Secret

Recommended pipeline stages

Stage	Purpose
Build	Compiles UiPath project from Git into a .nupkg artifact
Deploy to Dev	Deploys to Dev Orchestrator for immediate developer testing
Deploy to Test	Promotes to QA/Staging Orchestrator for formal testing
Deploy to Prod	Final deployment to live Production Orchestrator

Pipeline setup

1

Register UiPath tool

Tool Registry → +New Tool → search UiPath. Enter URL, Organization Name, Auth Type, Client ID, and Client Secret. Save and verify the connection test passes.

2

Add Build step

Step Setup: Tool = Build. Step Settings: SCM Type, Account, Repository, Branch. Set Build Type = UiPath, Script Type = Opsera for no-code automation. Opsera discovers project.json, resolves dependencies, compiles workflows, generates .nupkg, and applies versioning automatically.

3

Add Deploy steps

Click + for each environment stage. Step Setup: Tool = Deploy.

Step Settings

Field	Description
UiPath Tool	Registered UiPath tool from Tool Registry
Tenant	Orchestrator tenant to deploy to
Folder	Orchestrator folder (hierarchical path) for the package
Artifact Step	Pipeline step that produced the artifact to deploy
Run and Validate Job	When on: runs post-deployment validation. When off: deploys without validation.

4

Run and monitor

Click Start Pipeline. Under Run Logs, confirm the UiPath package is published, release is created, and job starts without errors.

Points to remember

• Use Opsera Script Type for the Build step — it handles the entire build lifecycle includingproject.jsondiscovery, dependency resolution, NuGet packaging, and versioning automatically.

• EnableRun and Validate Jobin deploy steps for non-production environments — this catches issues before they reach production Orchestrator.

• Each deployment stage should have its own Deploy step with a separate Tenant and Folder configuration — this ensures proper environment isolation.

• Rollback is triggered by rerunning the pipeline pointing to the last known stable version — Opsera does not auto-rollback to prevent unintended production changes.