Commit 935a8ada01
935a8ada01476de91352945057f5505e12bf124e
parent: 8e2dbc6807
Verified · cmc ci/build: success ci/test: skipped
cmc <hello@cleberg.net> · 2026-09-10 01:56 UTC
wiki: claim order stays oldest-first
A runner serving several repositories takes them oldest-first; a
repository that must never wait gets its own runner.
Closes #207
.gitbay/wiki/Admin.org
+4 −2
| @@ -399,8 +399,10 @@ Oldest-first is across everything the key may claim, so a repository |
| 399 | 399 | with a deep queue holds every other repository the same runner serves; |
| 400 | 400 | bay1 measured a 15-minute average wait on a day of merge request |
| 401 | 401 | stacks from one repository. A runner attached to one repository cannot |
| 402 | | be starved. Whether a runner serving several rotates across them is |
| 403 | | krz/gitbay#207. Nothing caps what an account queues: builds pending at |
| 402 | be starved. That is the rule, decided in krz/gitbay#207: a runner |
| 403 | serving several repositories takes them oldest-first, and an operator |
| 404 | who wants one repository never to wait on another runs a second |
| 405 | runner attached to it alone. Nothing caps what an account queues: builds pending at |
| 404 | 406 | once and schedule intervals down to a minute are unbounded, and a |
| 405 | 407 | build nothing claims stays pending. Since a build runs only on a |
| 406 | 408 | runner its owner attaches, the cost is rows and the queue numbers on |
.gitbay/wiki/CI.org
+3 −2
| @@ -25,8 +25,9 @@ runner attached to its repository (or one polling with a full-scope |
| 25 | 25 | admin key), and an untrusted build only by one started with |
| 26 | 26 | =-untrusted=. A repository with no runner attached queues builds |
| 27 | 27 | nothing claims. See the Users page. Among what a runner may claim it |
| 28 | | takes the oldest pending build; per-repository rotation when one |
| 29 | | runner serves several is krz/gitbay#207. There is no cap on how many |
| 28 | takes the oldest pending build, across every repository it serves; |
| 29 | a repository that must never wait on another gets a runner of its own |
| 30 | (decided in krz/gitbay#207). There is no cap on how many |
| 30 | 31 | builds an account queues or how often a schedule fires; that is |
| 31 | 32 | krz/gitbay#206. |
| 32 | 33 | |