You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's kinda hard to detect interactive user sessions in a bulletproof way
We really, really don't want to accidentally set --interactive for CI/PR/remote/server builds, because that manifests as "hard-to-diagnose build hang".
Agree. Critical to all of this is the ability for a user to force the interactive-ed-ness to off, which can always be done by explicitly specifying /interactive:false or equivalent.
/interactive:false can be difficult to add when MSBuild is only invoked by a third-party NPM package as part of a larger node.js build. Is there an environment variable to force noninteractive?
No description provided.
The text was updated successfully, but these errors were encountered: