Menu

1 / 2

Your GitHub Actions Bill Is Mostly Waiting: Measure Runner-Minutes Before You Optimise Anything

DEV Community: cicd·CodeOps·about 17 hours ago
#GZL1iZME
#devtocicd#devto#dev#minutes#workflow
Reading 0:00
15s threshold

Every team that says "CI is expensive" eventually gets asked the follow-up question: how expensive, exactly — and where? Most can't answer it. So the optimisation work starts with folklore ("add caching"), burns a sprint, and ends with a bill that looks about the same.

There is a cheaper order of operations: measure first, in one unit, ranked. The unit is runner-minutes per day, per workflow. Once you have that table, the waste stops being a vibe and becomes a list — and most of it is not slow tests. It's waiting, duplication, and runs nobody needed.

The honest framing first

Standard GitHub-hosted runners are free for public repositories . If your repo is public, your "cost" is developer waiting time, concurrency headroom, and habits that will follow you into private repos. If your repo is private — or you use larger runners — runner-minutes are literal money. Either way, the measurement is the same, and you should only ever claim savings in the unit that actually applies to you.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.