jglick Hey Jesse, I get that it's a no-no to try and modify the env global across multiple nodes. I'm curious what the expectations/best practices are for builds where we use multiple nodes and expect that the local env vars would be available within that node block scope.
i.e. I start a build on a "generic" node which does the checkout, some initial setup and stashes the results, then fires off parallel branches to run on different OSes/platforms with that source. I'm seeing that the env vars sent down to sh calls are actually coming from the initial node the job started on, which was a little surprising. (I have env vars set to point to things like Android NDK/SDK install paths on boxes, etc. it feels odd to have to explicitly run a shell script to get the real value from the node and then pass that into a withEnv block.)