Runner Management

This section introduces how to configure and use the Runner of AtomGit Action, including official hosted Runners, self-hosted Runners (hosts and Kubernetes), tag selection, and custom run images.

📄️ Using AtomGit Hosted Runners

Applicable scenarios: No need to build your own infrastructure, directly use the official resource pool Runner provided by AtomGit to execute pipeline tasks, suitable for most building, testing, and lightweight deployment scenarios.

📄️ Using Self-Hosted Runners

Applicable Scenarios: When the official hosted runners cannot meet the requirements—special hardware (GPU, specific architecture), internal network environment, custom toolchain, or large-scale parallelism—self-hosted runners can be deployed.

📄️ Choosing Runner Tags

Applicable Scenarios: When you need precise control over which Runner a job runs on — specifying operating system, architecture, resource specifications, or custom features (GPU, specific toolchains) — it is necessary to understand the tag matching rules.

📄️ Configure Runtime Image and Toolchain

Applicable Scenario: When the pre-installed toolchain on the hosted Runner does not meet the project requirements - needing a specific language version, dedicated dependencies, or a complete build environment - a custom Docker image can be specified using the container field.