How to avoid interactive mode on CI

[ScottRobbins]

How to avoid interactive mode on CI

[ScottRobbins]

It looks like there may be some standards around CI runners having an environment variable automatically present. You can see an example of someone guarding against them here: https://github.com/watson/ci-info/blob/master/index.js#L52

• Gitlab-CI uses CI: https://docs.gitlab.com/ee/ci/variables/predefined_variables.html
• Github Actions also uses CI: https://docs.github.com/en/free-pro-team@latest/actions/reference/environment-variables
• Jenkins uses BUILD_NUMBER, which is kind of an indication: https://wiki.jenkins.io/display/JENKINS/Building+a+software+project#:~:text=Jenkins%20Set%20Environment%20Variables%20%20%20%20Environment,build%20i%20...%20%2011%20more%20rows ...but also I don't love jenkins and a jenkins user could always add the CI environment variable themselves.

In the presence of this environment variable(s) I could avoid interactive input.

Still interested in what other good command line utilities do though. I would imagine in a large script you don't want it normally asking for input. I could do something like git where you don't get interactive mode unless you pass -i.

[ScottRobbins]

Should also not go interactive if not an interactive terminal

[ScottRobbins]

https://clig.dev/#interactivity