I think Github Actions is just a lead for Microsoft customers to use paid Azure DevOps. It is bad intentionally.
GitHub Actions is slowly killing engineering teams
201–210 of 219 posts
Re: GitHub Actions is slowly killing engineering teams
#202Re: GitHub Actions is slowly killing engineering teams
#203Things 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…
I think the main point is that you can configure environments to target from deployments.
Re: GitHub Actions is slowly killing engineering teams
#204Earlier 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?
Re: GitHub Actions is slowly killing engineering teams
#205Re: GitHub Actions is slowly killing engineering teams
#206Re: GitHub Actions is slowly killing engineering teams
#207Re: GitHub Actions is slowly killing engineering teams
#208The 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
#209Earlier 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…
Re: GitHub Actions is slowly killing engineering teams
#210Earlier 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.
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.