feat(pipeline): report deployed tool versions from the tools themselves
"What is running where" was answerable only by asking someone. Each tool now reports its own version on startup into a ToolVersion registry, shown on Pipeline → Machines. The worker's version moves out of config.json and into the assembly: a hand-maintained string on each machine is exactly the thing that goes stale, and a machine reporting a version it is not running is worse than no version at all. publish.ps1 stamps the git SHA via SourceRevisionId, so a deployed exe traces back to a commit (1.1.0+feb1c7b). The panel gains PANEL_VERSION, shown in its title and every diagnostics report, and pings on load. Staleness is derived rather than declared: the newest version seen for a tool is the benchmark, so updating one machine is what flags the rest. There is no expected-version list to keep in sync — which would have been one more thing to forget. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -434,6 +434,24 @@ Below them are two buttons:
|
||||
|
||||
---
|
||||
|
||||
## Versions
|
||||
|
||||
The panel's version is the `PANEL_VERSION` constant at the top of
|
||||
`VFXReviewConnector.jsx`. It appears in the panel title, in every diagnostics
|
||||
report, and is sent to the server when the panel loads.
|
||||
|
||||
**Pipeline → Machines → Deployed tool versions** then shows which version each
|
||||
workstation is running, alongside the render workers. Anything behind the newest
|
||||
version seen for that tool is flagged `→ rebuild to vX` — so updating one
|
||||
machine is what surfaces the ones still to do. No expected-version list to keep
|
||||
in sync; the newest thing reporting in is the benchmark.
|
||||
|
||||
**Bump `PANEL_VERSION` whenever you copy the .jsx to a workstation.** If two
|
||||
machines report the same version but behave differently, one of them was copied
|
||||
without the bump.
|
||||
|
||||
---
|
||||
|
||||
## Diagnostics and logging
|
||||
|
||||
Every button press is traced: what it tried, in what order, with the paths and
|
||||
|
||||
Reference in New Issue
Block a user