Faster GitHub Actions runners in one line
Change runs-on and a GitHub Actions job runs on Zode: standby runners, warm caches kept between jobs and a local Actions cache. The trust rules, and where it's slower.
3 min read
Most CI time isn't spent running tests. It is spent waiting for a machine, then rebuilding the same caches the last job already had. Zode runs GitHub Actions jobs on its own VMs and goes after both of those first.
Moving a job takes one line. Nothing else in the workflow changes.
The one-line switch
jobs:
test:
- runs-on: ubuntu-latest
+ runs-on: zode-4x8
Before that works, an owner or admin installs the Zode GitHub App once, in the console under Configure, CI, and picks the repositories.
| Label | vCPU | RAM |
|---|---|---|
zode or zode-2x4 | 2 | 4 GB |
zode-4x8 | 4 | 8 GB |
zode-8x16 | 8 | 16 GB |
zode-16x32 | 16 | 32 GB |
The runner image looks like GitHub's ubuntu-24.04. The job runs as the runner user in /home/runner/work, and actions/cache, the cache: option of the setup-* actions and Buildx type=gha keep working.
What that line gets you
Standby runners
A repository that ran a job in the last 30 minutes keeps a runner already booted and connected to GitHub. The next job of that size starts without waiting for a machine, in about 4 seconds. Standby time is not billed.
Warm snapshots
A green job on the default branch leaves its checkout, ~/.cache, ~/.npm, ~/go, the tool cache and Docker's state on a disk. The next job with the same repository, workflow, job, runner size and image starts from it. Attaching that disk takes under a tenth of a second.
A local Actions cache
Each node answers GitHub's cache API itself, so restores come from the node's disk instead of GitHub's storage, under GitHub's own branch rules.
Who may write a warm cache
A shared cache is a trust problem before it is a speed problem. If a pull request could write the disk the next main-branch job starts from, any contributor could poison your release build. So the rules are strict:
- Only a
push,scheduleorworkflow_dispatchrun on the default branch writes, and only when the job succeeded. - Pull requests read the shared snapshot but never write one. That includes
pull_request_target. - A pull request from a fork starts clean unless an owner or admin turns on fork reads.
- Before a snapshot is kept, credentials are scrubbed:
~/.docker/config.json,~/.npmrc,~/.netrc,~/.aws,~/.ssh, the GitHub CLI config and every git auth header.
We tested this live by planting a token in every one of those paths; it was gone in the next job. Every 7 days the next writing job also starts clean on purpose, so a build that only passes on a warm disk shows up. The details are in the warm snapshots docs.
The second line, when you want it
Sharding and test selection need to know which command runs your tests. Wrap it:
- - run: python -m pytest
+ - run: zode-ci test -- python -m pytest
zode-ci runs the command unchanged, passes its output through and exits with its exit code. It stores every test's result and duration. Test selection runs in shadow mode: it records what it would have skipped while still running the full suite, so you can see whether it would have missed anything before you trust it.
Where it is still slower
Honest numbers matter more than a headline. Start time is where Zode wins today. Run time per step is still slower than GitHub-hosted runners on many workloads, and we are working on it.
Two things to know when you compare:
- Use
ubuntu-24.04as the GitHub side, notubuntu-latest. GitHub'subuntu-latestmoved to 26.04 and Zode's CI image is 24.04. - If a job uses
actions/setup-go, setcache: falseon Zode. The warm disk already holds the module cache, and the action's own restore over it made Setup Go on helm's workflow take 67 to 107 seconds instead of 35.
Packages installed with apt are not kept between jobs; only the warm disk is. What the CI image still lacks against GitHub's is listed with every image release in PARITY.md.
Try it on one job
Pick your slowest job, change its runs-on, and push to the default branch twice: the first run writes the warm snapshot and the second starts from it. Then compare. The full guide is Move a workflow to Zode.
Try it: install the CLI, or start free in the console.
curl -fsSL https://zode.dev/install | sh