Studio Admin source control discovery and CI/CD pipeline management for building source-controlled Studio projects and updating published Orchestrator processes.

A coding agent can discover your Studio Admin source control state and wire up a CI/CD pipeline that builds a source-controlled Studio project and runs or updates an already-published Orchestrator process — without you touching the Studio Admin UI.

A pipeline binds two independent things: a source — a Studio project, standalone or inside a Solution, reached through an existing GitHub or Azure DevOps connection in Studio Admin — and a target — an Orchestrator process that's already published. The agent discovers both sides for you: which source control connections exist, which projects and Solutions they expose, and which published processes are available to bind to.

Once you pick (or the agent confirms) the source and target, it composes the pipeline definition, creates it, and can trigger a run in the same step — then follows the run's logs until it finishes.

This is distinct from CI/CD and automation, which covers running the uip CLI non-interactively inside your own pipeline. This skill builds and manages the Studio Admin pipeline resource itself.

This work is powered by the uipath-aops skill, which discovers Studio Admin source control state and creates, edits, and runs CI/CD pipelines. You can see it in the Skills catalog.

A first request might look like this:

"Create and run a CI/CD pipeline for this source-controlled Studio project."

The agent lists your available source control connections and published processes, confirms which pair you want, and creates the pipeline.

For the full picture of source control and CI/CD pipelines, see the Automation Ops pipelines documentation.