When should I self-host GitHub Actions runners? (part 1)

kevin@elyclover.com (Kevin Holmes) — Mon, 31 Jul 2023 10:00:00 +0000

As 2023 flies by and the Cybersecurity incidents making headlines continue to roll in, I would like to discuss self-hosting your own GitHub Actions infrastructure.

First, I always encourage teams to use hosted solutions when possible. The keyword here, and in most good systems engineering, is “where possible” - which can be the hardest part for teams to isolate and identify given their backstory, knowledge gaps, and regulatory environment(s). For instance, I’ve seen powerful DevOps, Infrastructure, or Platform engineering teams decide to self-host Actions Runner environments because they have the resources and buy-in from management. However, there’s no strong reason beyond the team wanting to do it and thinking they have the free cycles. This kind of thinking is a classic trap for engineering teams because the objective is a sexy one, and I can’t deny that. GitHub Actions are getting more popular by the day, and it’s certainly a hot topic among teams already using GitHub for source control or considering the move from competing well-established ecosystems like GitLab, Gerrit, Jenkins, and similar alternatives.

FedRamp on Ely Clover

When should I self-host GitHub Actions runners? (part 1)