Choose a runner
Choose RealHW capacity in three layers:
- Start with a GitLab-compatible SaaS tag for the generic runner shape.
- Add RealHW hardware markers when the job needs specialized hardware.
- Add
HW_*variables only when the job needs an explicit reservation or placement override.
Generic job
Section titled “Generic job”unit-tests: tags: - saas-linux-medium-amd64 script: - cargo testHardware-specific job
Section titled “Hardware-specific job”xdp-tests: tags: - saas-linux-large-amd64 - nic:tier:25g - nic:driver:mlx5_core variables: HW_NIC_TIER: "25g" script: - ./run-xdp-tests.shWhen to use variables
Section titled “When to use variables”Tags describe eligible runner capacity. HW_* variables describe what this job must reserve now.
Use variables for explicit CPU or memory overrides, NIC tier reservation, SR-IOV VF count, NUMA policy, hugepage size, and placement preference.