chore(runner): raise CI concurrency to 2 (parallel recipe testing) #8
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/runner-capacity-2"
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?
Raises
DRONE_RUNNER_CAPACITY1→2 so immich and plausible (both under active dev) can run CI in parallel.Safe on this node: full immich CI stack measured ~1GiB with ~5GiB free on the 7.6GiB cpx22; the harness janitor is already age-based + run-app-scoped (never reaps a concurrent in-flight run). Trade-off: a SIGKILL'd build's orphan now lingers up to the 2h janitor window (the run-start sweep can't reap a possibly-live run) — covered by the /upgrade-all start/end reap + sweep-orphans. Revert to 1 if OOM/IO contention appears.
⚠ Deploy restarts
drone-runner-exec, which kills any in-flight build — deploy when the runner is idle.@notplants