Catcrafts/catcrafts.net
Watch
2
0
Fork
You've already forked catcrafts.net
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CI: give the deploy runner a label of its own (catcrafts-deploy)
All checks were successful
Deploy / build-deploy (push) Successful in 7m17s
Details

Browse source 
A job goes to whichever runner carrying its label polls first, and the
`flatpak` label this job shared with imsd's package job is also on the
organisation-wide cx33-org-flatpak runner (registered 2026-10-14), which
has no deploy mounts, no Flatpak volume and defaults to an alpine image.
Crafter.Build's run 550 landed there on 2026-10-16 and failed before
building; runs 549 and 552 of this job reached the right runner only
because it polled first.

The repository's runner now declares `catcrafts-deploy:docker://archlinux:latest`
(a config edit and a service restart; labels are not part of the
registration), and the job asks for that. Nothing else changes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Jorijn van der Graaf 2026-10-17 00:22:50 +02:00
commit 15af22eea5
Signed by: jorijnvdgraaf
GPG key ID: 2937E59CDCC1BCFB
2 changed files with 25 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

18
deploy/README.md
View file

@ -83,14 +83,20 @@ systemctl reload caddy
## Runner configuration
The deploy job runs on a privileged runner registered to this repository alone
(`runs-on: flatpak`), not on the shared `arch-latest` runner. crafter-build is
the Crafter.Build Flatpak, and bubblewrap inside the job container needs the
privilege; imsd's package job is set up the same way. On the box since
2026-10-12:
(`runs-on: catcrafts-deploy`), not on the shared `arch-latest` runner.
crafter-build is the Crafter.Build Flatpak, and bubblewrap inside the job
container needs the privilege; imsd's package job is set up the same way. The
label is this repository's own on purpose: a job goes to whichever runner
carrying its label polls first, and imsd's `flatpak` label is also on the
organisation-wide `cx33-org-flatpak` runner (since 2026-10-14), which has no
mounts and defaults to an alpine image. Crafter.Build's run 550 (2026-10-16)
landed there and failed before building. On the box since 2026-10-12:
* `/etc/forgejo-runner/config-catcrafts.yaml`: label
`flatpak:docker://archlinux:latest`, `privileged: true`, cache proxy on port
34570.
`catcrafts-deploy:docker://archlinux:latest` (was `flatpak` until
2026-10-17), `privileged: true`, cache proxy on port 34570. Labels live in
this file; the runner declares them at start, so a label change is an edit
plus a service restart, never a re-registration.
* `forgejo-runner-catcrafts.service`, a copy of the imsd unit, working
directory `/var/lib/forgejo-runner-catcrafts`. Its `.runner` is the
registration: scope `Catcrafts/catcrafts.net`, name