[JIRA] (JENKINS-14569) PATH is not being injected correctly

Mon, 06 Aug 2012 01:41:09 -0700

No.

At first, I don't understand why EnvInject distinguishes PATH from Path on Windows, when standard Jenkins variable setup implementation does not behave this way.

Secondly, the issue is also about installing EnvInject makes standard environment setup working incorrectly. I used to have jobs which added to PATH within standard 'set environment variables' and these are no longer applied, even though I have not enabled any EnvInject option in the project. It seems that installing EnvInject itself breaks the way Jenkins handles environment variables for the build (or at least PATH variable). This is true for Unix-based build as well.

To reproduce the issue:

  • on the node set environment variable PATH
  • create a new free style build and tie it on this node
  • in the job check 'set environment variable' and add something to the PATH
  • int the build step use shell step and run 'echo ${PATH}'
  • notice that PATH does not contain modifications from standard settings

While I understand that this field is not part of EnvInject setup, I find it breaking since installing EnvInject is enough to break jobs that are set up like this (the jobs do not even need to have EnvInject configured).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to