Runner updates: a build that rolls back on one runner is held for the rest issue #326 closed: completed andymccall opened this 9 days ago · 0 comments

When a runner reports that it rolled back from flow X (it did not reach the hub after updating, or would not start), the hub should stop offering X to every other runner until an administrator lifts the hold, so one failed canary halts the rollout (docs/jetstream.md §8.2: a wave that is not healthy halts). Admin › Runners › Updates lists the holds, with who rolled back and why.