mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2026-05-13 02:04:38 +00:00
Add runner priority and fallback scheduling #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Woodpecker currently treats labels as hard filters. In a heterogeneous self-hosted setup there is no way to prefer one matching runner over another, or to fall back to a slower runner only when the preferred runner is unavailable.
Concrete case: we have two linux/arm64 runners:
Both can match platform=linux/arm64, but Woodpecker has no scheduler weight, priority, or fallback pool. The only current workaround is to remove eligibility from one runner, which means jobs wait instead of falling back.
Desired behavior
Add scheduler policy for runner preference, for example:
Why this matters
Labels are good for hard constraints such as platform or repository. They are not enough for operational scheduling policy when runners differ significantly in speed, cost, reliability, or availability.