Live data from Hacker News

GitHub Actions is slowly killing engineering teams

iankduncan.com

201–210 of 219 posts

Re: GitHub Actions is slowly killing engineering teams

#201
post #91

I think Github Actions is just a lead for Microsoft customers to use paid Azure DevOps. It is bad intentionally.

Azure DevOps doesn't have any hosted images above the minimum-sized ones... if we were ever going to move off of GitHub Actions, it wouldn't be to a service that required use to manage our own VMs/images.

Re: GitHub Actions is slowly killing engineering teams

#203

Things I dislike about GHA (on Enterprise Server) * Workflows are only registered once pushed to main, impossible to test the first runs in a branch. * MS/GH don't care much about GHES as they do github.com, I think they'd like to see it just die. Massive lack of feature parity. * Labels: If any of your workflows trigger from a label, they ALL DO. You can't target labels only to certain workflows, they all run and th…

> * Deployments: What is a deployment even doing? There is no management to deploy.

I think the main point is that you can configure environments to target from deployments.

Re: GitHub Actions is slowly killing engineering teams

#204

Earlier quoted context omitted.

Because my employer has already standardized on CF?

Oh. So when you say “May we please have terraform back?” You mean “May we please have terraform back at my employer?” Why are you posting such an employer specific request on a public forum?

Because it was meant as a rhetorical device, not a literal request.

Re: GitHub Actions is slowly killing engineering teams

#206
I keep everything simple, my complete orchestration is in a deploy.sh script that can run locally on my Mac or in AWS CodeBuild that is just either a provided Docker container or one that you can customize. My yaml file is simple - bash deploy.sh. It works anywhere - Azure containers jobs or GitHub Actions and any other build system that I can just hand it a Docker container

Re: GitHub Actions is slowly killing engineering teams

#208
People get overfixated on the runners. They don't matter. GHA, Buildkite, Jenkens, Gilab, doesn't matter. That isn't to say GHA isn't poo (it is and always has been poo) but it is to say it's not the actual problem.

The actual problem is using a bunch of unportable vendor YAML for literally anything.

Define your entire build + artifact publishing pipeline in something like Bazel, Nix, etc and completely decouple everything from the runner. This allows running it locally and also switching runners extremely easily if one of them is no longer to your liking.

Don't fall prey to the vendor YAML trap.

Re: GitHub Actions is slowly killing engineering teams

#209

Earlier quoted context omitted.

I did a BK search earlier in the article and ended on the same page, decided I couldn't be bothered to play those sort of games and clicked away. The GPs link actually looks rather interesting so I'll investigate, so take this a hate-it-folk vote.

Understandable; let me ask a a question. You don't want to play these sort of games (read a paragraph, enter a word). For you, browsing to find a compelling devtool, what makes you say, this is legit? Can you share examples of a couple of sites that do exactly what you are after? I say that not because we wanted the CLI homepage to be 'legit', the light context there is we needed a way to quickly change direction fro…

I'd never heard of BK before and I see some positive opinions on HN; I manage a small company's CI, we're really rather happy with GitLab CI, but I'm always on the lookout for something better. Clicking through to your page I'm looking to quickly find out what are the features, why it's different, how much it costs ... and for that a boring, routine website is what I'm hoping for. I'm very much not against the command-line (most places I work people complain that I use the command line when "there's this really good GUI"), but command-lines are hard, they need to be learned -- when I'm just looking for the outline as to whether it's worth digging further I really don't want to have to learn your command-line in order to get it, boring and routine is better. Just one grunt's personal opinion -- best of luck with the business!

Re: GitHub Actions is slowly killing engineering teams

#210

Earlier quoted context omitted.

I mean... They told you why it takes so long no? the runners come by default with loads of programming languages installed like Rust, Haskell, Node, Python, .Net etc so it sets all that up per user add. I would also question why your adding users on an ephemeral runner.

> I would also question why your adding users on an ephemeral runner. We use runners for things that aren't quite "CI for software source code" that does some "weird" stuff. For instance, we require that new developer system setup be automated - so we have a set of scripts to do that, and a CI runner that runs on those scripts.

Fair enough if you've some development environment automation and you want the CI to run it as well so CI is consistent with local development.

Don't know exactly what your doing but others(myself included) are using Mise or Nix on a per project basis to automate the development environment setup and that works well on GitHub Actions.

But I don't think useradd taking 30's on GitHub Actions is a bug or something they need to fix, they've explained why. Unsure about the sudo issues, did not read it carefully.

Post reply on HN