CI in one line
Move a GitHub Actions workflow to Groundbox by changing its runs-on line.
- Sign in with GitHub at app.groundbox.dev. The free plan needs no card.
- Install the Groundbox GitHub App on an organization or on your personal account, and pick the repositories it can see.
- Change one line in a workflow file, then push.
jobs:
test:
- runs-on: ubuntu-latest
+ runs-on: groundbox-4vcpu
steps:
- uses: actions/checkout@v4Nothing else in the workflow changes. Each job runs in a new VM that is destroyed when the job ends. The dashboard can open this pull request for you.
Sizes and labels
| runs-on | Size | Plan | Per minute |
|---|---|---|---|
groundbox-2vcpu | 2 vCPU · 8 GB | Free and paid | $0.003 |
groundbox-4vcpu | 4 vCPU · 16 GB | Free and paid | $0.006 |
groundbox-8vcpu | 8 vCPU · 32 GB | Paid | $0.011 |
A label also works with -ubuntu-2404 on the end, for example groundbox-4vcpu-ubuntu-2404. Jobs are billed by the second and stop at 6 hours. Runners are Linux x86-64.
The free plan has 3,000 minutes a month on 2 and 4 vCPU, 20 jobs at once, for private repositories.
Caches
The caches are on the same machine as the job, so nothing in the workflow changes to use them.
- Package mirrors: npm, PyPI, crates, apt and Docker Hub.
- Actions caches:
actions/cacheand the caches thesetup-*actions keep. - Docker layers: a stock
docker buildreuses layers from earlier builds, with no cache flags.
A layer is reused only when everything before it is unchanged. Copy the lockfile and install packages before you copy the rest of the source, so a code change does not reinstall every package:
COPY package.json pnpm-lock.yaml ./
RUN pnpm install --frozen-lockfile
COPY . .
RUN pnpm buildCaches are kept per team.
Migrate
groundbox migrate rewrites the runs-on lines in .github/workflows and prints the diff. Name where you are coming from: github, blacksmith, depot or namespace.
groundbox migrate github --dry-run # print the diff, change nothing
groundbox migrate githubci wait
groundbox ci wait waits for the CI of the commit checked out here and exits 0 when it passed, 1 when it failed and 4 when it timed out. On failure it prints the failing step's log. An agent runs it after a push and reads the result.
git push
groundbox ci waitIf a job doesn't start
The CI runs page in the dashboard shows held jobs and the reason: out of free minutes or credit, the team's limit on jobs at once, or no free capacity. Jobs already running always finish.