-
Notifications
You must be signed in to change notification settings - Fork 5
Specifying The Runner Type
The default server type is cx22, which is an Intel, 2 vCPU, 2GB RAM shared-cpu x64 instance.
✋ Note: | You can use the --default-type option to set a different default server type. |
---|
You can specify different x64 server instance type by using the type-{name} runner label. The {name} must be a valid Hetzner Cloud server type name such as cx22, cpx21 etc.
For example, to use an AMD, 3 vCPU, 4GB RAM shared-cpu x64 instance, you can define the runs-on as follows:
job-name:
runs-on: [self-hosted, type-cpx21]
The default server type is cx22, which is an Intel, 2 vCPU, 2GB RAM shared-cpu x64 instance. Therefore, in order to use ARM64 runners, you must specify the ARM64 server instance type by using the type-{name} runner label. The {name} must be a valid ARM64 Hetzner Cloud server type name such as cax11, cax21 etc. which correspond to the Ampere Altra, 2 vCPU, 4GB RAM and 4 vCPU, 8GB RAM shared-cpu ARM64 instances, respectively. You must also specify a valid ARM image using the image-arm-{type}-{name} runner label.
For example, to use the Ampere Altra, 4 vCPU, 8GB RAM shared-cpu ARM64 instance, running the ubuntu-22.04 image, you must define the runs-on as follows:
job-name:
runs-on: [self-hosted, type-cax21, image-arm-system-ubuntu-22.04]
Developed and maintained by the TestFlows team.
- Home
- Installation
- Quick Start
- Getting Started Tutorial
- Basic Configuration
- Specifying the Maximum Number of Runners
- Specifying the Maximum Number of Runners Used in Workflow a Run
- Recycling Powered‐Off Servers
- Skipping Jobs
- Using Custom Label Prefix
- Jobs That Require the Docker Engine
- Specifying The Runner Type
- Specifying The Runner Location
- Specifying The Runner Image
- Specifying The Custom Runner Server Setup Script
- Specifying The Custom Runner Server Startup Script
- Disabling Setup or Startup Scripts
- Specifying Standby Runners
- Specifying Logger Configuration
- Listing All Current Servers
- Opening The SSH Client To The Server
- Deleting All Runners and Their Servers
- Using a Configuration File
- Specifying SSH Key
- Specifying Additional SSH Keys
- Running as a Service
- Running as a Cloud Service
- Scaling Up Runners
- Scaling Down Runners
- Handling Failing Conditions
- Meta Labels
- Estimating Costs
- Listing Images
- Deleting Images
- Creating Custom Images
- Program Options