UiPath CLI user guide

uip solution pack <solutionPath> <outputPath> [--name <name>] [--version <version>] [--login-validity <minutes>]
uip solution pack <solutionPath> <outputPath> [--name <name>] [--version <version>] [--login-validity <minutes>]

• <solutionPath> (required) — Path to a solution directory (containing a .uipx manifest) or a .uis file.
• <outputPath> (required) — Output directory where the .zip package will be written. The directory must exist; it is not created for you.

• -n, --name <name> — Package name. Defaults to the solution folder name (or the .uis file's base name). The packaged .zip is named <name>.<version>.zip.
• -v, --version <version> — Package version. Defaults to 1.0.0. Appears in the output filename and is the value passed to --package-version on deploy run.
• --login-validity <minutes> — Minimum minutes before token expiration to trigger a refresh. Defaults to 10. Only relevant when pack's internal bundling step needs to resolve remote resources.

Minimal​

uip solution pack ./my-solution ./dist
uip solution pack ./my-solution ./dist

Common — pin name and version for a CI build​

uip solution pack ./my-solution ./dist --name invoices --version 1.2.0
uip solution pack ./my-solution ./dist --name invoices --version 1.2.0

Scripting — capture the output path for the publish step​

PKG=$(uip solution pack ./my-solution ./dist --version 1.2.0 --output-filter "Data.Output" --output plain)
uip solution publish "$PKG"
PKG=$(uip solution pack ./my-solution ./dist --version 1.2.0 --output-filter "Data.Output" --output plain)
uip solution publish "$PKG"

{
  "Code": "SolutionPack",
  "Data": {
    "Package": "my-solution.1.2.0.zip",
    "Output": "./dist/my-solution.1.2.0.zip"
  }
}
{
  "Code": "SolutionPack",
  "Data": {
    "Package": "my-solution.1.2.0.zip",
    "Output": "./dist/my-solution.1.2.0.zip"
  }
}

• Package — basename of the generated .zip.
• Output — path to the .zip on disk, relative or absolute depending on <outputPath>.

• uip solution publish — uploads the packed .zip to the tenant solution feed.
• uip solution upload — alternative path that uploads the solution to Studio Web for interactive editing instead of packaging it for deployment.
• uip solution deploy run — deploys a published package to Orchestrator.

• Your first pipeline — pack → publish → deploy run walkthrough.
• uip solution overview.