Urgent.News

What's breaking now, across thousands of outlets.

Tech

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

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.…

Your GitHub Actions bill is largely contingent upon waiting, duplication, and unnecessary runs. Before optimizing, it's crucial to measure the runner-minutes per day for each workflow. The unit is measured by calculating the wall-clock time for each completed run, dividing it by the days covered, and summing it per workflow. Once the data is available, you can identify waste patterns, such as cold caches, redundant builds, oversized matrices, unused runs, frequent nightly rebuilds, and employing expensive runners for insignificant tasks. By addressing these issues in order, you can significantly reduce costs and improve efficiency.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

MikroTik PCC Load Balancing: How to Set Up 2 ISPs + Failover (RouterOS v7)

Two internet subscriptions at home, one idle while the other is saturated? MikroTik's PCC (Per Connection Classifier) is the standard fix: the router splits user connections across both ISPs, so their…

  • MikroTik's PCC balances connections across two ISPs, utilizing combined capacity.
  • On RouterOS v7, create WAN interface list, routing tables, and mangle rules for PCC setup.

Silent Failure #10: The Reply That Never Posted, With an Exit Code of 0

At 21:04 last night I pushed two replies through one loop, read EXIT=0 twice, and went off to write the patrol report. One of the two had never been posted anywhere.

  • Reporter found one reply failed to post despite exit code of 0
  • Script assumed zero exit code meant success, but it printed nothing
  • Redirecting script output resolved the issue between poster and browser

More from Wednesday 18 November →