Programming

26250 readers

631 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

GitHub Actions Is Slowly Killing Your Engineering Team - Ian Duncan (www.iankduncan.com)

submitted 8 hours ago by mesamunefire@piefed.social to c/programming@programming.dev

6 comments fedilink hide all child comments

Why GitHub Actions is the Internet Explorer of CI, and why Buildkite offers a better path forward for teams that care about developer experience.

you are viewing a single comment's thread
view the rest of the comments

[–] jtrek@startrek.website 4 points 5 hours ago

Sounds about right.

I'm using GitHub actions at work because this place is extremely dysfunctional, and I can just add GitHub actions without it being a whole "research spike planning meeting impact analysis" six week journey.

I took it from "there are absolutely no checks and Bob broke the environment because he pushed up a change that's just invalid syntax" to... well, I couldn't make it block the build on failures but at least now when Bob breaks it again I can point to the big red X and ask why he merged with an error.