runner
A machine running the runner application that picks up a queued job, runs its steps and reports the result.
In more detail
When a workflow is triggered, each job waits in a queue until a runner claims it. The runner streams logs back while steps run and finally reports pass or fail. GitHub-hosted runners are fresh virtual machines destroyed after one job; self-hosted runners are machines you own and keep.
Related terms
- GitHub-hosted runner — A virtual machine that GitHub creates for a single job and destroys when the job ends.
- self-hosted runner — A runner you install and operate on your own hardware or cloud machine, selected with the self-hosted label.
- runs-on — The workflow key that says which kind of runner a job needs, by image label or by self-hosted labels.
- runner application — The program installed on a runner machine that registers with GitHub, waits for jobs and executes them.
- GitHub Actions — GitHub's built-in automation service that runs workflows, written as YAML files in a repository, on runners when events happen.
- workflow (GitHub Actions) — A YAML file in the .github/workflows folder of a repository that names its triggers and the jobs to run.
Taught in
- What Is a Pipeline? — Continuous Integration & Continuous Delivery Pipelines
- Runners: Where Code Executes — Continuous Integration & Continuous Delivery Pipelines
- Workflows, Jobs, Steps, and Actions — Continuous Integration & Continuous Delivery Pipelines
- Continuous Integration — DevOps & Site Reliability Engineering
- The Workflow That Ran On A Stranger's Pull Request — GitHub Actions (GH-200) Exam Prep
- How GH-200 Asks: Pacing, Weights And Stems — GitHub Actions (GH-200) Exam Prep
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Workflow Structure: Jobs, Env, Services, Commands And Anchors — GitHub Actions (GH-200) Exam Prep
- Expressions, Contexts And The If That Is Always True — GitHub Actions (GH-200) Exam Prep
- Matrices, Needs And Concurrency: The Shape Of A Run — GitHub Actions (GH-200) Exam Prep
- Outputs, Artifacts, Caches And Job Summaries — GitHub Actions (GH-200) Exam Prep
- Why It Ran, Why It Did Not: Reading Runs, Jobs And Checks — GitHub Actions (GH-200) Exam Prep
- Failed Runs: Debug Logging And Re-Running The Right Jobs — GitHub Actions (GH-200) Exam Prep
- Workflow Templates: Sharing Workflows Across An Organization — GitHub Actions (GH-200) Exam Prep
- Three Kinds Of Action: JavaScript, Docker Container Or Composite — GitHub Actions (GH-200) Exam Prep
- action.yml: Inputs, Outputs, Runs And Branding — GitHub Actions (GH-200) Exam Prep
- Building And Debugging A JavaScript Action — GitHub Actions (GH-200) Exam Prep
- Composite And Docker Actions: Troubleshooting And Immutable Releases — GitHub Actions (GH-200) Exam Prep
- Governing Actions: Allow Lists, SHA Pinning And Rulesets — GitHub Actions (GH-200) Exam Prep
- GitHub-Hosted And Larger Runners: Specs, Software And Networks — GitHub Actions (GH-200) Exam Prep
- Self-Hosted Runners At Scale: Labels, Groups And ARC — GitHub Actions (GH-200) Exam Prep
- Usage, Billing And The Audit Log — GitHub Actions (GH-200) Exam Prep
- GITHUB_TOKEN: Least Privilege, Job By Job — GitHub Actions (GH-200) Exam Prep
- Script Injection: When An Issue Title Becomes Code — GitHub Actions (GH-200) Exam Prep
- OIDC: Cloud Access Without Stored Keys — GitHub Actions (GH-200) Exam Prep
- Faster And Cheaper: Where The Minutes Go — GitHub Actions (GH-200) Exam Prep
- YAML-Reading Sprint: What Happens When This Runs? — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep
- The Merge Request That Deployed To Production — GitLab Certified CI/CD Associate Exam Prep
- How The Exam Works: Fifty Questions, No Notes — GitLab Certified CI/CD Associate Exam Prep
- Continuous Integration, Delivery And Deployment: One Keyword Apart — GitLab Certified CI/CD Associate Exam Prep
- From Push To Runner: How GitLab Starts A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Anatomy Of .gitlab-ci.yml, And Three Ways To Check It — GitLab Certified CI/CD Associate Exam Prep
- Jobs And Stages: Who Waits, Who Runs, Who Gets Skipped — GitLab Certified CI/CD Associate Exam Prep
- Rules, Workflow Rules And The Legacy only And except — GitLab Certified CI/CD Associate Exam Prep
- Reuse With extends And include, And What Survives The Merge — GitLab Certified CI/CD Associate Exam Prep
- Caching: Dependencies That Survive Between Pipelines — GitLab Certified CI/CD Associate Exam Prep
- CI/CD Variables: Where Values Come From, And Which One Wins — GitLab Certified CI/CD Associate Exam Prep
- The Container Registry: Build, Tag, Push, Clean Up — GitLab Certified CI/CD Associate Exam Prep
- Package Registries: Publishing With The Job Token — GitLab Certified CI/CD Associate Exam Prep
- Reading Security Results: The Merge Request And The Vulnerability Report — GitLab Certified CI/CD Associate Exam Prep
- Runner Types And Executors: Who Runs The Job, And Where — GitLab Certified CI/CD Associate Exam Prep
- Registering Runners And Routing Jobs With Tags — GitLab Certified CI/CD Associate Exam Prep
- Debugging Pipelines: The Graph, The Errors, The Logs — GitLab Certified CI/CD Associate Exam Prep
- Faster Pipelines: Minutes You Can Win Back — GitLab Certified CI/CD Associate Exam Prep
- Pipeline Clinic: Five Tickets, Five Fixes — GitLab Certified CI/CD Associate Exam Prep
- Recall Sprint: Knowing It Cold, With No Docs And No AI — GitLab Certified CI/CD Associate Exam Prep
- Final Mock And Review: One Question Short — GitLab Certified CI/CD Associate Exam Prep