Self-hosted Actions runners without dedicating a whole machine to CI
GitHub's standard self-hosted runner is convenient when you can give it a dedicated machine, but it's only one runner per machine.
But keeping a separate box just for CI can get expensive, and I'd rather not have build scripts and leftover containers messing with a machine I also use for other things.
What I like about gh-runnerd is that it runs multiple runners on one machine, with each job getting its own fully isolated VM.
When the job finishes, the whole VM gets destroyed, and the next job starts fresh.
Is anyone here using this or something similar?
u/AroundTech — 11 days ago