Runner updates: policy, test groups and the update a runner is offered issue #322 closed: completed andymccall opened this · 1 comment
andymccall set labels feature ·
referenced by 4 changes on 26 Oct 2026
andymccall
Done: Admin › Runners › Updates sets the policy per site, owner, test group and runner (nearest wins: on/off, channel, window, dry run), oh runner-updates and its API read and set it, and runners ask GET /api/v1/flow/runner/update every 15 minutes and install what they are offered (OxygenFlow, oxygenflow#84). What is left of self-updating runners (fetching through the swarm, waves and health) is on oxygenflow#84.
andymccall closed ·
Step 2 and 3 of self-updating runners (OxygenFlow docs/jetstream.md §8.2, oxygenflow#84). Updates are off unless chosen; the site, an owner, a test group and a runner each may set updates on or off, a channel (stable, canary or a version), a window of hours and dry run, and the nearest setting wins. A test group is chosen runners or a percentage of the site's (or an owner's) runners, taken by a stable hash of each runner's id so the same machines are in it every rollout and 10% sits inside 50%. GET /api/v1/flow/runner/update tells a runner its policy and the build it should run (from the site's runner releases repository, asset flow-linux-ARCH); the runner reports back what it did. Admin › Runners › Updates sets it.