3 ms·

After troubleshooting a couple issues with the GitHub Actions Linux admin team, and their decision to not address either issue, I'm highly skeptical of investin

by rsyring 8mo ago

After troubleshooting a couple issues with the GitHub Actions Linux admin team, and their decision to not address either issue, I'm highly skeptical of investing more in GitHub Actions: - Ubuntu useradd command causes 30s+ hang [1] - Ubuntu: sudo -u some-user unexpectedly ends up with environment variables for the runner [2] 1: https://github.com/actions/runner-images/issues/13048 https://github.com/actions/runner-images/issues/13048 2: https://github.com/actions/runner-images/issues/13049 https://github.com/actions/runner-images/issues/13049

Storment33 8mo ago
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.
- Marsymars 8mo ago
  > 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.
  - Storment33 8mo ago
    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.
    - Marsymars 8mo ago
      > 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. Oh we don't even run it in applications' CI, the environment automation is an entirely separate CI workflow. The intention isn't consistency between dev/CI, the environment automation CI effectively just serves to ensure that the automations actually run without error, and adds some explicit responsibility for anyone who's adding a new dependency. > 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. Yeah, agreed. Tangential, our dev setup CI is fairly slow, which tends to be fine - it runs a couple orders of magnitude less frequently than our app CI.

by rsyring 8mo ago

Storment33 8mo ago

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.

Marsymars 8mo ago
> 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.
- Storment33 8mo ago
  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.
  - Marsymars 8mo ago
    > 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. Oh we don't even run it in applications' CI, the environment automation is an entirely separate CI workflow. The intention isn't consistency between dev/CI, the environment automation CI effectively just serves to ensure that the automations actually run without error, and adds some explicit responsibility for anyone who's adding a new dependency. > 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. Yeah, agreed. Tangential, our dev setup CI is fairly slow, which tends to be fine - it runs a couple orders of magnitude less frequently than our app CI.