Maybe this is intended behaviour (or maybe I'm doing something wrong) but if i have this test pipeline:
/tmp is not on PATH:
However if I just switch wtihEnv and nvm around:
/tmp is now on the PATH:
Why does this matter to me? Because our Shared Library currently has...
... all over the place and while refactoring it by moving the order of theses statements around isn't a biggie it's not very nice to have code that only works if the statements are in a certain order.
So tl;dr: please change the behaviour of the code not to overwrite PATH set by withEnv or advise on some other way to work around this.
Content of withNode:
withMaven() uses withEnv internally: