Commit 5bd5b27bc1

5bd5b27bc1f94219d6fa081aeeac4ca07d29fbfc

parent: 53af684817

Verified · cmc ci/build: success ci/test: failure

cmc <hello@cleberg.net> · 2026-09-07 03:37 UTC

deploy, wiki: the runner claims the isolation canary too

A runner scoped by -repos never claims a build outside it, so the
nightly cmc/ci-smoke job sat pending. Listed alongside krz/gitbay.

Ref #144

Layout: unified · split

.gitbay/wiki/Admin.org +2
@@ -503,6 +503,8 @@ management and =ReadWritePaths= for podman's store under
503make read-only. Those paths are prefixed =-= so they are ignored when 503make read-only. Those paths are prefixed =-= so they are ignored when
504absent: the drop-in installs on unprepared hosts too, and a unit that 504absent: the drop-in installs on unprepared hosts too, and a unit that
505refused to start would stop every build. 505refused to start would stop every build.
506The nightly canary on =cmc/ci-smoke= only runs if the runner's =-repos=
507names that repository too; a scoped runner claims nothing else.
506=gitbay-runner-prune.timer= prunes unused images weekly, as the runner's 508=gitbay-runner-prune.timer= prunes unused images weekly, as the runner's
507user: rootless storage belongs to that user, and root's prune would not 509user: rootless storage belongs to that user, and root's prune would not
508see it. An unpruned image store on a 40GB host is a slow outage. 510see it. An unpruned image store on a 40GB host is a slow outage.
deploy/gitbay-runner.override.conf +5 −1
@@ -23,6 +23,10 @@
23# would otherwise make read-only. Prepare the host with 23# would otherwise make read-only. Prepare the host with
24# deploy/runner-podman-setup.sh before deploying a runner that isolates. 24# deploy/runner-podman-setup.sh before deploying a runner that isolates.
25[Service] 25[Service]
26# cmc/ci-smoke is the nightly isolation canary; a runner scoped to named
27# repositories never claims a build it is not scoped to, so the canary
28# must be listed or its scheduled build waits forever.
29#
26# -cpus 3 of the host's 4 leaves a core for gitbayd and sshd while a build 30# -cpus 3 of the host's 4 leaves a core for gitbayd and sshd while a build
27# runs. No -memory: the e2e suite peaks past 5GB of the 7GB, and a cap 31# runs. No -memory: the e2e suite peaks past 5GB of the 7GB, and a cap
28# that kills it is an outage rather than a limit (#144). 32# that kills it is an outage rather than a limit (#144).
@@ -41,7 +45,7 @@
41# End it with the service. 45# End it with the service.
42ExecStopPost=-/usr/bin/pkill -u ci-runner -x catatonit 46ExecStopPost=-/usr/bin/pkill -u ci-runner -x catatonit
43ExecStart= 47ExecStart=
44ExecStart=/usr/local/bin/gitbay-runner -remote git@127.0.0.1 -workdir /var/lib/gitbay-runner/work -poll 5s -timeout 45m -repos krz/gitbay -isolation podman -image localhost/gitbay-ci:1 -cpus 3 48ExecStart=/usr/local/bin/gitbay-runner -remote git@127.0.0.1 -workdir /var/lib/gitbay-runner/work -poll 5s -timeout 45m -repos krz/gitbay,cmc/ci-smoke -isolation podman -image localhost/gitbay-ci:1 -cpus 3
45Nice=10 49Nice=10
46CPUWeight=30 50CPUWeight=30
47IOWeight=30 51IOWeight=30