Expand description
How many warm runners each repository’s pool wants (ADR 0050, 0058): its warm while the repository is active, by
its jobs of the last hour and the hours of the day its jobs usually come, plus the jobs for the pool its workflow
runs seen so far are expected to queue still, from the history. Pure: the engine reads the history and the clock
and passes them in.
Structs§
- Attempt
- An attempt of a workflow run: a re-run keeps the run’s ID, with the next attempt, and queues its jobs anew.
- Burst
- What a workflow’s runs are expected to queue for one pool.
- Learned
- What warm runners learn from the history: when each repository’s jobs come, and how many jobs its workflows’ runs queue.
- Runs
- The workflow runs seen lately, by attempt: their jobs not queued yet get warm runners.
- Seen
- A job the history saw queued.
Constants§
- ACTIVE_
AFTER - How long after a repository’s last job it stays active.
- LOOKBACK
- How far back the history is read, in milliseconds: 14 days.
Functions§
- target
- How many warm runners a pool with
warmconfigured wants:warmwhile it isactive, plus the jobs its runs are expected to queue still (remaining). None withwarm = 0.