uipath-cli
latest
false
- 概要
- はじめに
- 概念
- Using UiPath CLI
- 使用ガイド
- CI/CD recipes
- コマンド リファレンス
- 概要
- 終了コード
- Global options
- uip codedagent
- uip docsai
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- プロジェクトを作成
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-workflow-examples
- pack
- 元に戻す
- run-file
- search-templates
- start-studio
- stop-execution
- uia
- uip traces
- 移行
- Reference & support
UiPath CLI user guide
最終更新日時 2026年5月7日
uip solution publish uploads a solution .zip — produced by uip solution pack — to the tenant's solution feed. Once a package is published, it is visible to uip solution packages list and can be deployed with uip solution deploy run.
Publish is an authenticated operation. Run uip login first, or pass --tenant to target a specific tenant within your authenticated organization.
Synopsis
uip solution publish <packagePath> [--tenant <tenant-name>] [--login-validity <minutes>]
uip solution publish <packagePath> [--tenant <tenant-name>] [--login-validity <minutes>]
The command honours the global options and returns the standard exit codes.
引数
<packagePath>(required) — Path to a.zippackage produced byuip solution pack. The file must exist and have a.zipextension; anything else fails with aFailureresult.
オプション
-t, --tenant <tenant-name>— Tenant to publish into. Defaults to the tenant selected during authentication.--login-validity <minutes>— Minimum minutes before token expiration to trigger a refresh. Defaults to10.
例
Minimal
uip solution publish ./dist/my-solution.1.0.0.zip
uip solution publish ./dist/my-solution.1.0.0.zip
Common — target a specific tenant
uip solution publish ./dist/my-solution.1.0.0.zip --tenant Production
uip solution publish ./dist/my-solution.1.0.0.zip --tenant Production
Scripting — chain pack → publish and capture the package version key
uip solution pack ./my-solution ./dist --version 1.2.0
KEY=$(uip solution publish ./dist/my-solution.1.2.0.zip --output-filter "Data.PackageVersionKey" --output plain)
echo "Published version key: $KEY"
uip solution pack ./my-solution ./dist --version 1.2.0
KEY=$(uip solution publish ./dist/my-solution.1.2.0.zip --output-filter "Data.PackageVersionKey" --output plain)
echo "Published version key: $KEY"
Data shape (--output json)
{
"Code": "SolutionPublish",
"Data": {
"Status": "Published successfully",
"PackageVersionKey": "a1b2c3d4-0000-0000-0000-000000000001",
"PackageName": "my-solution",
"PackageVersion": "1.0.0"
}
}
{
"Code": "SolutionPublish",
"Data": {
"Status": "Published successfully",
"PackageVersionKey": "a1b2c3d4-0000-0000-0000-000000000001",
"PackageName": "my-solution",
"PackageVersion": "1.0.0"
}
}
PackageVersionKey— GUID identifying this specific version of the package in the tenant feed.PackageName/PackageVersion— the values passed to (or defaulted by)pack; re-use them ondeploy run --package-name --package-version.
Version conflicts
Publishing a package whose name + version already exists in the feed fails with a descriptive error. Increment the version in your build — typically via pack --version … — before republishing. The error instructions point to this same remediation.
Related commands
uip solution pack— produces the.zipto publish.uip solution packages list— see published versions.uip solution packages delete— remove a published version.uip solution deploy run— deploy the published package to Orchestrator.
参照
- Your first pipeline — pack → publish → deploy run walkthrough.
- Authentication — session management.
uip solutionoverview.