-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
I upgraded Jenkins to 1.458 and envinject from 1.36 to 1.44. After the upgrade all my jobs that did not use envinject were getting their WORKSPACE variable set to another jobs that did use envinject WORKSPACE. Downgraded envinject to 1.36 and the problem went away.
Here's an edited log that shows initially the workspace is correct, even after EnvInject line, but when the shell script runs, it is wrong.
Also, I don't know why EnvInject is even being run for this job since it is not enabled anywhere...
[EnvInject] - Preparing an environment for the build.
Building on master in workspace -correct-workspace-
Updating http://svn....
At revision 36652
no change for http://svn.... since the previous build
No emails were triggered.
[bronze-bin] $ /bin/sh -xe /tmp/hudson6983282044770433158.sh
+ echo -some-other-jobs-workspace-
[JENKINS-13348] EnvInject overriding WORKSPACE variable
Jim Searle
created issue -
Gregory Boissinot
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Jim Searle
added a comment - Thanks. I am sure... I will try something on our test server and get back to you.
Jim Searle
added a comment - Thanks. I am sure... I will try something on our test server and get back to you. Gregory Boissinot
added a comment - Did you have time to test it?
Thanks in advance. Gregory Boissinot
added a comment - Any update? Gregory Boissinot
added a comment - I'm closing the issue at the moment because I cannot reproduce it without more inputs.
Do not hesitate to reopen it when you will have more information.
Thanks in advance.
Gregory Boissinot
added a comment - I'm closing the issue at the moment because I cannot reproduce it without more inputs.
Do not hesitate to reopen it when you will have more information.
Thanks in advance. Gregory Boissinot
made changes -
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Mikko Mattila
added a comment - I'm seeing this same issue with Jenkins 1.454 & the EnvInject plugin 1.74-SNAPSHOT from yesterday. I had 1.72 when I initially encountered this. Not reopening the bug yet, because I have no further useful information.
Mikko Mattila
added a comment - I'm seeing this same issue with Jenkins 1.454 & the EnvInject plugin 1.74-SNAPSHOT from yesterday. I had 1.72 when I initially encountered this. Not reopening the bug yet, because I have no further useful information. Mikko Mattila
added a comment - The problem appears to get fixed by upgrading Jenkins core to 1.489.
Mikko Mattila
added a comment - The problem appears to get fixed by upgrading Jenkins core to 1.489. 
Strange behavior.
I don't know where it is from and I can't reproduce it.
Could you try to isolate it?
Are your sure?