GitHub · GH-200
Runners at scale
GH-200 · Lesson 12 of 16 · 1:47:59
YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗
In this lesson
Prepare for the GH-200 exam (GitHub Actions). In this lesson: GitHub-hosted runners with their preinstalled software, tool cache, and setup actions, larger runners, self-hosted runners with labels, runner groups, routing, ephemeral runners, and autoscaling, networking requirements and IP allow lists, and troubleshooting runners with their status, the config script's check, and their logs. Includes three original practice questions.
Preview the topics
- Contoso’s self-hosted runners serve its private repositories, and the team wants a new public repository to use them too, for faster builds. Why is that risky?
- Contoso’s store backend only accepts a short list of addresses in its firewall, and the release jobs run on standard GitHub-hosted runners. What should the team do?
- A Contoso job has been queued for an hour, with the runs-on labels self-hosted, linux, and gpu. The GPU runner shows as idle, with those labels, in a runner group. What should the team check first?