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.
This story alone was enough to cause me to abandon GitHub actions permanently. I’d have easily gotten bitten by that had I expanded CI to the extent that these gigantic companies are using it.
Ironically, I am one of these people building get up action CI pipelines that automate large multi-service multi-team deployments across different cloud vendors and regions.
It’s all a bit of a pain in the ass and. Actions don’t really provide many of the nice controls and safety guarantees we would want.
However, GitHub actions is relatively straightforward to implement and relatively easy to operate.
It’s just very easy for you to foot gun