Docs/Get started

Quickstart: CI runners

Run your GitHub Actions jobs on Anvil's machines by changing one line. Caches, Docker layers and git checkouts come from the same disk as the job.

diff

 jobs:
   test:
-    runs-on: ubuntu-latest
+    runs-on: anvil-4cpu

You need the Anvil app installed on the repository (see Quickstart: code review).

Let Anvil open the pull request #

Open CI → Run on Anvil.
Pick the repository and a runner size. anvil-4cpu suits most builds.
Check the preview: every runs-on line that changes, file by file, and the jobs that stay where they are.
Click Open pull request, then merge it on GitHub.

The next run of those workflows runs on Anvil. Watch it under CI → Compute while it runs.

Or edit the line yourself #

Change runs-on in any job of .github/workflows/*.yml, commit and push:

yaml

jobs:
  test:
    runs-on: anvil-4cpu

Label	CPUs	Memory
`anvil-2cpu`	2	6 GB
`anvil-4cpu`	4	12 GB
`anvil-8cpu`	8	24 GB

Hosted on Anvil #

Repositories hosted on Anvil already run CI here: put a workflow in .gitea/workflows/ or .github/workflows/ with runs-on: ubuntu-latest. See Find failing, slow and flaky CI.

Next #

Move workflows to Anvil runners Matrices, self-hosted jobs, and going back.
Runner sizes and labels Caching, Docker builds, sticky volumes and limits.
Find failing, slow and flaky CI Run history, failure diagnosis, flaky tests and log search.