14fb43b959
Some checks are pending
check / gate (push) Waiting to run
Surveyed ten repos: 36 of 36 ACTIVE workflows already say runs-on: [self-hosted, linux, x64]. They were written for the self-hosted runners that died when the repos went private — so advertising those three labels makes every one of them runnable AS-IS. No workflow edits, no rewrites. Correcting an earlier note in this plan: 'ban ubuntu-latest' was wrong as stated. All 11 occurrences are tagged '# runner-lint-allow — CD/hosted-only; disabled, manual until CD mission'. They are deliberately hosted-only and deliberately off. They are correct as written and should not be 'fixed'. I generalised that doctrine from one repo without surveying. The survey disagreed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
59 lines
2.3 KiB
YAML
59 lines
2.3 KiB
YAML
# act_runner configuration (G7.1).
|
|
#
|
|
# Labels are EXPLICIT and PINNED. `ubuntu-latest` is banned (G7.5): all four
|
|
# windy-registry workflows use it and every single run fails, because a
|
|
# self-hosted runner has no such label unless you invent one. A workflow that
|
|
# names a label nobody provides queues forever and looks like a hung CI system
|
|
# rather than a typo.
|
|
|
|
log:
|
|
level: info
|
|
|
|
runner:
|
|
file: /data/.runner
|
|
capacity: 4 # concurrent jobs; Veron has 24 cores, dind is capped at 12
|
|
timeout: 30m
|
|
shutdown_timeout: 3m
|
|
insecure: false
|
|
fetch_timeout: 5s
|
|
fetch_interval: 2s
|
|
labels:
|
|
# windy-git's own workflows.
|
|
- "veron-1:docker://catthehacker/ubuntu:act-22.04"
|
|
- "linux-x64:docker://catthehacker/ubuntu:act-22.04"
|
|
# THE FLEET'S EXISTING CONVENTION. Surveyed 2026-08-12 across ten repos:
|
|
# 36 of 36 active workflows say `runs-on: [self-hosted, linux, x64]`.
|
|
# They were written for the self-hosted runners that died when the repos
|
|
# went private, so advertising these three labels makes every one of them
|
|
# runnable AS-IS — no workflow edits, no rewrites.
|
|
#
|
|
# A job asking for [self-hosted, linux, x64] matches only if the runner
|
|
# advertises ALL THREE, so all three are declared separately.
|
|
- "self-hosted:docker://catthehacker/ubuntu:act-22.04"
|
|
- "linux:docker://catthehacker/ubuntu:act-22.04"
|
|
- "x64:docker://catthehacker/ubuntu:act-22.04"
|
|
|
|
cache:
|
|
enabled: true
|
|
dir: /data/cache
|
|
|
|
container:
|
|
# Empty = act creates a NETWORK PER JOB and removes it afterwards.
|
|
#
|
|
# This started as `bridge` for isolation, which was a mistake in both
|
|
# directions. It broke service containers — Postgres came up healthy but the
|
|
# job could not resolve the name `postgres`, because service DNS aliases only
|
|
# exist on a per-job network — and it was *weaker* isolation, since every
|
|
# concurrent job shared one flat bridge and could see its neighbours.
|
|
#
|
|
# A per-job network is both correct and stricter. Still no route to the forge:
|
|
# these networks live inside the dind daemon, which has no forge attachment
|
|
# at all.
|
|
network: ""
|
|
privileged: false
|
|
options:
|
|
workdir_parent: /workspace
|
|
valid_volumes: [] # a job cannot bind-mount anything from the daemon host
|
|
docker_host: "-" # do NOT expose the runner's own docker socket to jobs
|
|
force_pull: false
|