forgejo: dedicated deploy-arm64 runner so CI cannot starve site deploys #8
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/runner-deploy-arm64"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a second Forgejo runner instance on the Pi declaring only the
deploy-arm64label.deploy-site.ymlmoves to it, so a long onionwirecibuild (runs-on: docker) can no longer hold the only slot a site deploy can land on. Labels are disjoint in both directions: deploys cannot occupy the Pi'sdockerrunner either, whose capacity 1 serializes onionwire jobs sharing theonionwire-target-civolume.Runner registration persists on the Pi host at
/opt/siriusdevops/runner-deploy/data/runner.ini; the token secretforgejo-runner-deploy-arm64-tokenis created out-of-band (not in Git).