Runners: registration, Admin → Runners, history, drain/disable/remove issue #45
closed: completed andymccall opened this · 0 comments
andymccall
H12a, hub side (oxygenhub#41). Runners in the database: one-time registration tokens on Admin → Runners, and POST /api/v1/flow/runners/register binding the runner's key. hub.toml runners are tracked too. Claims record the runner and its description. The Runners page shows status, key, machine, labels, capacity, running jobs and last seen, with drain, disable, resume and remove. Each runner's page shows its totals and job history.
H12a, hub side (oxygenhub#41). Runners in the database: one-time registration tokens on Admin → Runners, and
POST /api/v1/flow/runners/registerbinding the runner's key. hub.toml runners are tracked too. Claims record the runner and its description. The Runners page shows status, key, machine, labels, capacity, running jobs and last seen, with drain, disable, resume and remove. Each runner's page shows its totals and job history.