As of 2026-03-24. Survey conducted for CLO-985.
- Pipeline 1 (image components via
push-tank-builds.yml): Working - Pipeline 2 (binary/goreleaser components via
goreleaser-component-release-to-tank.yml): Broken —workflow_runtrigger never fires successfully - Pipeline 3 (manual build/release): Working, used as safety valve
- Pipeline 4 (atlas): Manual only, no continuous automation
- Pipeline 5 (external images): Manual only, digest-pinned
| Component | Type | Pipeline | Tank automation | Known issue |
|---|---|---|---|---|
| core-api | image | push-tank-builds | Working | — |
| infer | image | push-tank-builds | Working | — |
| sandbox | image | push-tank-builds | Working | — |
| sandbox-daemon | image | push-tank-builds | Working | — |
| sandbox-node-daemon | image | push-tank-builds | Working | — |
| bridge-sandbox | image | push-tank-builds | Working | — |
| gvisor-installer | image | push-tank-builds | Working | — |
| web-assistant | image | push-tank-builds + push-tank-ui-builds | Working | — |
| pool | binary | goreleaser-to-tank | BROKEN | workflow_call doesn't fire workflow_run. Fix: #32781 |
| splash | binary | goreleaser-to-tank | Untested | No release since workflow created (March 20); should work on next tag push |
| backuprestore | script | goreleaser-to-tank | Untested | Same timing issue as splash |
| vscode-extension | binary | goreleaser-to-tank | Untested | Last release was March 17, before workflow created. Should work when vscode/release-* PR merged |
| vs-extension | binary | goreleaser-to-tank | No workflow | No release workflow exists at all |
| atlas | image (external repo) | manual only | None | No automation to detect/ingest new atlas images |
| sandworm | external image | manual only | None | Not even in manual-component-build choices |
| envoy-gateway | external image | manual only | None | Digest-pinned, manual update |
| envoy-proxy | external image | manual only | None | Digest-pinned, manual update |
| postgres | external image | manual only | None | Digest-pinned, manual update |
| poolside-database-client | external image | manual only | None | Digest-pinned, manual update |
| ubuntu-base | external image | manual only | None | Digest-pinned, manual update |
goreleaser-component-release-to-tank.yml watches for workflow_run completions of:
| Watched workflow | Why it doesn't work |
|---|---|
pool-release |
Only invoked via workflow_call from ui-create-release-pr. GitHub does NOT fire workflow_run events for workflow_call. |
splash-release |
Triggered by tag push (would work), but no splash release has happened since the goreleaser workflow was created March 20. |
ui-vscode-assistant-release |
Fires on every PR to main but with conclusion="skipped" (branch doesn't match vscode/release-*). Goreleaser checks conclusion == 'success' and skips. |
BackupRestore release |
Last successful run was March 20 02:46 UTC, hours before the goreleaser workflow was merged later that day. |
Result: 200+ workflow_run-triggered runs, all skipped. Zero successful automated tank releases for any binary component.