Why GitHub Actions is the Internet Explorer of CI, and why Buildkite offers a better path forward for teams that care about developer experience.
Why GitHub Actions is the Internet Explorer of CI, and why Buildkite offers a better path forward for teams that care about developer experience.
Lot of complaining for issues that are easily side stepped, but maybe cos I’ve learnt it all already, but it does fill the article with lots of words.
The byo compute and logs thing is half the rant which has never even been a problem for me in the last 4 years on GH.
Not sure between config and programming? You literally can choose that yourself.
Biggest issue for CI for me is how to get CI secrets locally… which I don’t know a good answer for.
Nix is great but try getting your whole team / org on it…