0
GitHub Actions Getting Expensive? We Cut CI Costs to a Quarter With a One-Line Change
TL;DR: A team shares how migrating CI runners reduced GitHub Actions costs by about 75% and shortened the slow tail, achieved with a single-line change. They compare migrations from GitHub-hosted to Blacksmith to Namespace and emphasize cost considerations for AI-driven, high-frequency CI.
The article documents migrating CI runners twice: GitHub-hosted to Blacksmith, then Blacksmith to Namespace. Each migration yielded roughly one-quarter the per-run cost, a 37% shorter p90 tail, and fewer silent-running runs (down to zero). The authors highlight that AI-enabled development inflates both run counts and task complexity, driving CI cost growth. They also stress staying on free tiers when possible, noting public repos get free standard runners and private repos have monthly minute limits that influence migration decisions. The piece includes measured methods, findings, and a failed migration case for context.
Question for the room: Have you moved off GitHub-hosted runners, and what one-line change or approach helped you cut costs the most?
— via dev.to
Add a comment
0/2000