Raises DRONE_RUNNER_CAPACITY 1→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
Raises `DRONE_RUNNER_CAPACITY` 1→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
Lets two recipes be tested in parallel (operator request — immich + plausible under
active dev at once). Safe on the current node: measured a full immich CI stack at
~1GiB with multiple GiB free on the 7.6GiB cpx22, and the janitor is already
age-based + run-app-scoped so it never reaps a concurrent in-flight run. Updates the
stale '28GiB node' comment. Revert to 1 if OOM/IO contention shows up.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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