To start using GitRunners you just need to change your
jobs.[job-name].runs-on property in the workflow files:
GitRunners allows you to use different kind of runners to match your use-cases. To select the operating system, number of virtual CPUs or hardware architecture you can simply change the label replacing
ubuntu-2204 with the OS of your choice,
2vcpu with the amount of CPU required by your job and
x64 with e.g.
Please check the following sections to know the available options.
# Ubuntu 20.04 on 8 cores with x64 architecture runs-on: gitrunners-ubuntu-2004-x64-8vcpu # Ubuntu 22.04 on 4 cores with arm64 architecture runs-on: gitrunners-ubuntu-2204-arm64-4vcpu
GitRunners currently support the following OS images:
|Label Value||Supported Architecture||OS|
|Ubuntu 22.04 LTS|
|Ubuntu 20.04 LTS|
|Windows Server 2022|
|Windows Server 2019|
If you need more images, please contact support.
You can customize the CPU/RAM of the runner by setting the right value on the
x64 actually exposes 2 OS-level CPU cores but only uses 50% of the core capacity.
1vcpu is only supported for Linux runners.
For instance, if you want to use the 8 vCPUs runner you just need to use the following line:
If you would like to explore other CPU/RAM selections, please contact support.
Hardware architecture selection
GitRunners currently provides
arm64 runners. If you need to run your jobs on different architectures, please contact support.
GitRunners images are based on the images used by Github managed runners and we do a best-effort to keep them aligned. Github doesn't support ARM64 architecture though, in this case some software is not available (e.g. Edge/Chrome drivers).
Wrong labels and typos
The label list in the
runs-on property might have typos or unsupported combinations.
If any error is detected in the label list, GitRunners silently fails. You can detect these errors when the job remains queued for a very long time. Jobs queued for more than 24h eventually fail.