5 ms·

> Obviously, a command line tool doesn't have the luxury of an interactive setup, Why would the command line tool not have the option of an interactive setup?

• alkonaut 4y ago
  > Why would the command line tool not have the option of an interactive setup? Typically because (at least if it's already shipped) there are hard expectations about what it will do. E.g. that it shouldn't block waiting for input. That might screw headless/CI uses. A shipped product probably also doesn't have the luxury of using a /noninteractive or /noTelemetry or requiring an env car or similar to block it, because the CI scripts are already written. You can have it ask the user (block waiting for input) if its given a NEW command line option. But you can't do it in the absence of that option. That's why, for a shipped product, it's so much easier to make it opt out. The alternative would be to make it opt in via command line switch or env var - which would obviously be so rare that there is no point in doing it at all.
  • jonhohle 4y ago
    How many CI environment are (or at least should be) connected to the internet to begin with? That almost certainly eliminates the possibility of reproducible builds but also opens all kinds of security issues. (I know sandboxes builds are not common place, but they really should be.)
    • alkonaut 4y ago
      > How many CI environment are (or at least should be) connected to the internet to begin with No idea. If I had to make a guess I'd say 99%?