Back to articles
The 3-line YAML mistake that quietly drains your GitHub Actions minutes (and how I built a local parser to catch it)
NewsDevOps

The 3-line YAML mistake that quietly drains your GitHub Actions minutes (and how I built a local parser to catch it)

via Dev.to DevOpsShubham

We’ve all been there. You want to ensure your open-source library or SaaS works across all operating systems, so you proudly write this beautiful, innocent-looking matrix strategy in your .github/workflows/ci.yml : jobs : test : runs-on : ${{ matrix.os }} strategy : matrix : os : [ ubuntu-latest , windows-latest , macos-latest ] Looks harmless, right? What GitHub’s documentation buries in the fine print is the Runner Multiplier Tax . While Ubuntu runs at the base rate ($0.008/min), Windows costs 2x more, and macOS costs a staggering 10x more ($0.080/min). If your test suite takes 15 minutes to run, that single macos-latest line just cost you $1.20 per run . If you have a team pushing 10 commits a day, you are burning hundreds of dollars on macOS runners for code that probably only needed Linux testing. The Problem: Bill Shock is a lagging indicator By the time you see the GitHub billing dashboard at the end of the month, the damage is already done. I wanted a way to see the exact cost

Continue reading on Dev.to DevOps

Opens in a new tab

Read Full Article
2 views

Related Articles