Skip to content
Get started
The runner’s field guide

Know your runners.
Find your stride.

Practical guides for the questions that come
before, during and after your first job.

Practical notes
12 guides
GETTING STARTED01

Start with a runner. Build up to a fleet.

What a self-hosted GitHub Actions runner is, how a job reaches one, persistent versus ephemeral runners, autoscaling, security and what you take on.

5 MIN READ
ARCHITECTURE02

All the runners. None of the Kubernetes.

Choose between a simple runner, a Docker container, Zoomies and a runner service. Run ephemeral GitHub Actions jobs on your own hosts without a cluster.

4 MIN READ
HOME LAB03

Good hardware deserves another lap.

Plan GitHub Actions runners on machines you own: which home-lab hardware suits which jobs, where the controller goes, and what happens when a box is off.

5 MIN READ
OPERATIONS04

A job is waiting. Find out why.

Diagnose a queued GitHub Actions job: check labels, runner groups, Zoomies pool limits, host capacity, image startup and registration in order.

6 MIN READ
OPERATIONS05

Disposable runners. Useful memories.

Keep Go, npm, pip, Maven and Docker build caches between ephemeral runners. Configure Zoomies cache scopes and reuse builds safely across jobs and hosts.

12 MIN READ
GETTING STARTED06

A smaller leap than you think.

Move workflows off GitHub-hosted runners: the migration wizard rewrites runs-on across repositories and opens one pull request each, showing the diff first.

14 MIN READ
ARCHITECTURE07

A fresh start for every job.

What an ephemeral GitHub Actions runner is, why one job per runner keeps CI clean and safer, and how Zoomies registers, runs and destroys one per job.

5 MIN READ
ARCHITECTURE08

A little more room to run.

How Zoomies scales self-hosted GitHub Actions runners with the job queue on your own machines, which settings bound it, and why a queued job still waits.

4 MIN READ
GETTING STARTED09

Your hardware. Your call.

What running a self-hosted GitHub Actions runner fleet involves, what Zoomies handles, what it leaves to you, and when a managed service is the better choice.

7 MIN READ
ARCHITECTURE10

Put a runner in its place.

Running GitHub Actions runners in Docker: what one runner container gives you, three ways a job can get Docker, and how Zoomies makes an autoscaling fleet.

5 MIN READ
OPERATIONS11

More repositories. One happy pack.

Share self-hosted GitHub Actions runners across repositories: where GitHub allows registration, how one fleet serves an organisation, and keeping repos apart.

6 MIN READ
GETTING STARTED12

Count more than the minutes.

Does GitHub Actions cost money? Hosted runner pricing, free minutes per plan, the postponed self-hosted charge, and the sums for running your own.

5 MIN READ

Less reading. More running?

The quick start gets straight to your first working setup.

Run your first job