From the course: Advanced GitHub Actions
Unlock the full course today
Join today to access over 24,200 courses taught by industry experts.
GitHub-hosted runners vs. self-hosted runners - GitHub Tutorial
From the course: Advanced GitHub Actions
GitHub-hosted runners vs. self-hosted runners
- [Instructor] The GitHub Actions Runner is a software application. The runner application manages all the jobs, steps and actions in our workflows. It's an open-source application hosted on GitHub.com However, we usually think of a runner in terms of a compute platform. This includes any hardware like the CPU and memory, the operating system, and any programs and tools our workflows, and actions need. GitHub provides runners for the Actions service that we can use out of the box. These are virtual machines hosted by GitHub with the runner application already installed. However, we can also use self-hosted runners that we deploy and manage ourselves. This option gives us more control over the compute environment where our jobs run. Let's take a look at the differences between using these two types of runners along with the pros and cons of both. GitHub hosted runners provide a decent amount of hardware for most…
Contents
-
-
-
-
-
-
(Locked)
Self-hosted runners introduction50s
-
(Locked)
GitHub-hosted runners vs. self-hosted runners5m 27s
-
(Locked)
Configure a self-hosted runner4m 33s
-
(Locked)
Use a self-hosted runner in a workflow1m 43s
-
(Locked)
Challenge: Configure a self-hosted runner with a label1m 54s
-
(Locked)
Solution: Configure a self-hosted runner with a label6m
-
(Locked)
-
-