Programming

26271 readers

190 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 2 days ago by mesamunefire@piefed.social to c/programming@programming.dev

29 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

[–] douglasg14b@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

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