A common CI mistake: upgrading to a bigger runner before checking what the job is actually waiting on.
In RunsOn v3, each job gets CPU/memory/disk/network/I/O charts directly in the GitHub Actions UI by default.
No action, no OTEL backend, no CloudWatch setup.
I don't like advertising third-party products, but my testimonial is up on https://t.co/X7MZkqJt5N, and it's worth a look. @crohr has made something amazing.
We need an easy way to run benchmarks on bare-metal nodes via GitHub Actions, and nothing else compares. 12/10 product👌
After struggling with Actions Runner Controller (ARC) and Kubernetes-based runners, we've switched to https://t.co/JWSn0ds6mw for GitHub Actions infrastructure - eliminating the complexity of managing both Kubernetes clusters and runner scaling.
https://t.co/m7Rx5uJdwa
Am I the only one loosing my mind over github actions ? In the last days / weeks I've seen so many unexplained flakiness / random errors. Can't wait to migrate to https://t.co/xbpzEEOJ5m
While some are busy rebranding for the summer, I'm shipping, and people notice! Now close to 450k daily GitHub Actions runners, up from 400k just two weeks ago 🤯