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

22
.forgejo/workflows/deploy.yaml
View file

@ -13,15 +13,19 @@ concurrency:
jobs:
build-deploy:
# `flatpak` is a privileged runner registered to this repository alone
# (/etc/forgejo-runner/config-catcrafts.yaml on the box, label
# flatpak:docker://archlinux:latest): crafter-build is the Crafter.Build
# Flatpak, and bubblewrap inside the job container needs the privilege.
# The same runner carries the two deploy bind mounts (/deploy, /deploy-app)
# and a docker volume at /var/lib/flatpak that keeps the installed Flatpak
# and its Sdk between runs. Same route as imsd's package job; see
# deploy/README.md "Runner configuration".
runs-on: flatpak
# `catcrafts-deploy` is a privileged runner registered to this repository
# alone (/etc/forgejo-runner/config-catcrafts.yaml on the box, label
# catcrafts-deploy:docker://archlinux:latest): crafter-build is the
# Crafter.Build Flatpak, and bubblewrap inside the job container needs the
# privilege. The same runner carries the two deploy bind mounts (/deploy,
# /deploy-app) and a docker volume at /var/lib/flatpak that keeps the
# installed Flatpak and its Sdk between runs. Same route as imsd's package
# job, but under a label of its own: imsd's `flatpak` label is also on
# the organisation-wide runner (cx33-org-flatpak, since 2026-10-14), which
# has no mounts and defaults to alpine, and a job goes to whichever runner
# with the label polls first. Crafter.Build's run 550 (2026-10-16) failed
# that way. See deploy/README.md "Runner configuration".
runs-on: catcrafts-deploy
env:
# Which crafter-build. `stable` is the branch Crafter.Build publishes
# from its release tags, `beta` follows every push to its master (the