title: Jenkins Global Environment variables vs. node system variables?
body: <p>I notice that with our Jenkins 1.625.2, setting a Environment Variable for <em>all nodes</em> via <code>jenkins/configure -&gt; Global properties -&gt; Environment variables</code> <strong>only</strong> work, iff the environment variable in question is <strong>not</strong> already defined in the Windows system environment of a node.</p>
  
  <p>That is, if the Windows user that runs the Jenkins Slave process already has the environment variable FOOBAR, the setting FOOBAR in the global Jenkins Config has no effect on this node, whereas if the envvar is not there, then jobs run on the node will get it set to the global Jenkins config value.</p>
  
  <p>Does anyone know if this is intended behavior, a bug, or whether I may be missing something to get the global setting override the system envvar on the Windows node?</p>