OXYGENHUB

Releases 1

OxygenHub 0.9.6 v0.9.6 · ✔ signed by Andy McCall · andymccall ·

Trust and audit
  • A highlighting test no longer fails a busy machine's gate (issue #327): it timed a debug build against a release build's 500 ms; debug builds now have 3 s, still far below what highlighting the line would take.
  • oh runner-updates and its API (issue #322): site administrators read every level's update settings, the test groups, each runner's policy and offer, and the held builds (GET /api/v1/admin/runner-updates); oh runner-updates set group:canary --updates on --window 02-05 changes one level, keeping what is not given (PUT …/settings, 422 saying what is wrong); oh runner-updates lift 0.4.0 offers a held build again (POST …/holds/{version}/lift).
  • A build that rolls back on one runner is held for the rest (issue #326): when a runner reports it rolled back from flow X (it did not reach the hub after updating, or would not start), the hub offers X to no other runner, saying why, until an administrator lifts the hold on Admin › Runners › Updates, which lists each held build with the runner and the reason. One failed canary halts the rollout. Migration 0097.
  • Finished work moves to Done (issue #325): a card whose issue closes (on its page, through the API, or by a change's closes #N), or whose proposal lands or closes, moves to its board's column for finished work. A new board's Done is that column, and so is each existing board's column named Done; a column's menu turns it on or off (one column of a board). Archived cards stay archived.
  • A WASM job's placement names no image (issue #323): a job on the WASM tier was placed saying its runner "fetches the image from the hub"; it has none, so the line now starts with what the runner is doing (andymccall/windows-runner-demo run issue #1).
  • Runner updates: policy, test groups and the offer (issue #322): Admin › Runners › Updates sets where runner builds come from (a repository whose releases carry flow-linux-ARCH files, and flow-windows-x86_64.exe for Windows runners) and who takes them. Updates are off unless chosen; the site, an owner, a test group and a runner may each set updates on or off, a channel (stable, canary or a version), a window of hours (UTC) and dry run, and the nearest setting wins, each setting on its own. A test group is chosen runners or a percentage of the site's (or an owner's) runners, by a stable hash of each runner's id, so a share is the same machines every rollout and 10% sits inside 50%. GET /api/v1/flow/runner/update tells a runner its policy, where each setting came from, and the build to install (its BLAKE3, to check the download against); POST takes what the runner did, shown on the page and in the audit log. An organisation's owners set the same for their own runners in the organisation's Settings › Runner updates: the organisation's setting, test groups of its runners (chosen, or a percentage), and each runner's own; nothing of the site's or another owner's. Pins OxygenFlow's main.

Assets