uip rpa build

uip rpa build compiles a UiPath Studio project. It runs the workflow analyzer (unless skipped) and the workflow compiler against the project, but does not produce a .nupkg. Use it when you want to validate that a project compiles cleanly without packaging it — typical inner-loop or CI gate. Reach for uip rpa pack when you also need a NuGet package for upload.

Warnung:

Runtime-Anforderungen

• .NET runtime must be available on the runner — the workflow compiler is .NET-backed. See Breaking changes — .NET runtime.
• Windows runner for Windows projects. Cross-platform projects (targetFramework: "Portable") build on any OS. Windows projects (targetFramework: "Windows") require a Windows runner. Windows - Legacy projects require uip rpa-legacy. See uip rpa overview for the project-flavor matrix.

Synopsis

uip rpa build <projectDir> [options]

• <projectDir> — path to the Studio project (a directory containing project.json).

Optionen

Markieren	Beschreibung
--skip-analyze	Skip the workflow-analyzer step. Useful when analysis runs as a separate pipeline stage via uip rpa analyze.
--governance-file-path <path>	Path to a governance/policy rules file consumed by the analyzer.
--governance-file-type <type>	Type of governance file (the underlying packager validates the choice — run uip rpa build --help on a live install for the accepted set).
--detailed-log-path <path>	Write a detailed compiler/analyzer log to the given path.
--exclude-configured-sources	Ignore user/machine NuGet sources during dependency resolution. Use to enforce a hermetic build against --nuget-sources-config-path only.
--nuget-sources-config-path <path>	Path to a NuGet sources configuration file.
--log-level <level>	Compiler log level. Defaults to Warn.

For the complete option list on your installed tool version, run:

uip rpa build --help

Beispiele

# Build a project — fail the step on any compile or analyzer error
uip rpa build ./MyProject

# Build without re-running the analyzer (analysis runs in a separate CI stage)
uip rpa build ./MyProject --skip-analyze

# Build with governance enforcement
uip rpa build ./MyProject \
  --governance-file-path ./policies/governance.json

When to use build vs pack

Use case	Befehl
Validate a project compiles in CI before merging	uip rpa build
Produce a .nupkg for upload to Orchestrator or a feed	uip rpa pack
Validate dependencies resolve and types compile, no governance	uip rpa build --skip-analyze
Run governance gates only, no compile output	uip rpa analyze

pack does a build internally, so a separate build step before pack is redundant unless the two stages live in different pipeline jobs.

Related

• uip rpa pack — build and package into a .nupkg.
• uip rpa analyze — run only the workflow analyzer.
• uip rpa restore — restore dependencies; a clean build needs them on disk.

Siehe auch

• RPA tool overview
• Global options
• Exitcodes