UIP 解决方案发布

Syntax and options for `uip solution publish`, which uploads a solution `.zip` to a solution feed.

uip solution publish uploads a solution .zip — produced by uip solution pack — to a solution feed. By default the package lands in the tenant feed; pass --personal-workspace to target the current user's Personal Workspace feed instead, or --feed <name-or-key> to target a specific folder 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.

备注：

A published package is not yet deployed. Publishing only uploads the .zip to a feed — it does not create an Orchestrator folder, provision resources, or make the package runnable. Deploy it with uip solution deploy run before it appears in the processes list or can be started as a job.

大纲

uip solution publish <packagePath> \
  [--personal-workspace | --feed <name-or-key>] \
  [--package-name <name>] [--package-version <version>] \
  [--wait] [--timeout <seconds>] [--poll-interval <ms>] \
  [--login-validity <minutes>]

该命令遵循全局选项，并返回标准退出代码。

参数

• <packagePath> (required) — Path to a .zip package produced by uip solution pack. The file must exist and have a .zip extension; anything else fails with a Failure result. A .nupkg (a single project's package, e.g. from uip maestro flow pack) is explicitly rejected — pack the enclosing solution instead.

选项

长	值	默认	描述
--personal-workspace	标记	关闭	Upload into the current user's Personal Workspace feed instead of the tenant feed. Resolves the workspace folder key from Orchestrator automatically. Mutually exclusive with --feed.
--feed <name-or-key>	text	—	Publish into a feed by its name or folder key (from solution feeds list) instead of the tenant feed. Mutually exclusive with --personal-workspace.
--package-name <name>	text	name from the .zip	Publish under this name instead of the one the .zip was packed with. Rewrites the archive's solutionMetadata.json in memory (with a fresh package version key) — the file on disk is untouched, and bundled project packages keep their own names/versions. Only works on a package produced by uip solution pack.
--package-version <version>	text	version from the .zip	Publish under this version instead of the one the .zip was packed with. Use it to clear a "version already exists" rejection when you have the packed .zip but not the solution source, without re-packing. Same in-memory rewrite as --package-name.
--wait	标记	关闭	Wait until the published package reaches Ready or Active state before returning.
--timeout <seconds>	秒	360	Package-state polling timeout (only relevant with --wait).
--poll-interval <ms>	ms	5000	Milliseconds between package state polls.
--login-validity <minutes>	分钟	10	Minimum minutes before token expiration to trigger a refresh.

示例

最小

uip solution publish ./dist/my-solution_1.0.0.zip

Republish the same .zip under a new version

uip solution publish ./dist/my-solution_1.0.0.zip --package-version 1.0.1

Use this when the feed rejected the package because its name+version already exists and you have the .zip but not the solution source. --package-name works the same way for the name.

Publish to the current user's Personal Workspace

uip solution publish ./dist/my-solution_1.0.0.zip --personal-workspace

Publish into a named feed

uip solution publish ./dist/my-solution_1.0.0.zip --feed Finance

脚本编写 —chain pack → 发布并捕获包版本密钥

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"

数据形状（--输出 json）

{
  "Code": "SolutionPublish",
  "Data": {
    "Status": "Package is published to Orchestrator but not yet deployed",
    "PackageVersionKey": "a1b2c3d4-0000-0000-0000-000000000001",
    "PackageName": "my-solution",
    "PackageVersion": "1.0.0",
    "State": "Ready",
    "NextSteps": "Package is published to Orchestrator but not yet deployed. Deploy/activate it into an Orchestrator folder before it appears in the processes list or can be started as a job."
  }
}

• PackageVersionKey — GUID identifying this specific version of the package in the feed.
• PackageName / PackageVersion — the values from the package (or the --package-name/--package-version override); re-use them on deploy run --package-name --package-version.
• State — only present when --wait was used; the terminal package state (Ready or Active).

版本冲突

Publishing a package whose name + version already exists in the target feed fails with a descriptive error. Either:

• Increment the version and re-pack: uip solution pack <solution-path> <output-path> --version <new-version>, or
• Republish the same .zip under a new version without re-packing: uip solution publish <package-path> --package-version <new-version>.

相关命令

• uip solution pack — 生成.zip以发布。
• uip solution feeds list — find a feed's name or key for --feed.
• uip solution packages list — 查看已发布版本。
• uip solution packages delete — 删除已发布版本。
• uip solution deploy run — 将已发布的包部署到 Orchestrator。

另请参阅

• 您的第一个管道— 打包 → 发布 → 部署运行演练。
• 身份验证— 会话管理。
• uip solution概述。