Run GitHub CI on self-hosted runners - #69
Merged
Merged
Conversation
Switch all active workflow jobs from GitHub-hosted ubuntu-latest to self-hosted runners. The build job already has cache-detection logic targeting the local Squid proxy (192.168.13.3:3128), which is only reachable from self-hosted runners on the local network; running on GitHub-hosted runners silently skipped that cache. The deploy and Claude PR-review jobs move to self-hosted for consistency. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
simoncoles
marked this pull request as ready for review
July 23, 2026 19:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switches all active GitHub Actions jobs from GitHub-hosted
ubuntu-latesttoself-hostedrunners.main.ymlbuildubuntu-latestself-hostedmain.ymldeployubuntu-latestself-hostedclaude.ymlclaude-respondubuntu-latestself-hostedWhy
The
buildjob already contains cache-detection logic that targets a local Squid proxy at192.168.13.3:3128, with a comment noting it is "silently skipped when unreachable (e.g. GitHub-hosted runners)." That cache is only reachable from runners on the local network, so running on GitHub-hosted runners quietly bypassed it every time. Moving the jobs toself-hostedlets CI actually use that cache. Thedeployand Claude PR-review jobs are moved for consistency so the whole pipeline runs on the self-hosted fleet.The
self-hostedlabel is applied automatically to every self-hosted runner, so this targets the fleet without depending on any custom label naming.Notes / prerequisites
These jobs require self-hosted runners to be registered and online for the repository (or its org). In particular:
buildjob uses acontainer:image, so the runner host needs Docker available.deployjob needs outbound SSH (port 1970) tocrumpet.amphora.cloud.If a narrower runner group or custom labels are preferred (e.g.
[self-hosted, linux, docs]), theruns-onvalues can be tightened — happy to adjust.Test plan
yaml.safe_loadparses both workflow files without errorruns-on: self-hostedbuildjob on this PR🤖 Generated with Claude Code
Generated by Claude Code