[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Wisen Tanasa commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I'm hitting the same issue with EnvInject 1.89 and Jenkins 1.553. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
lacostej commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I am hitting the same issue. EnvInject 1.89 and jenkins 1.532.3 and WORKSPACE got set into hudson.EnvVars.masterEnvVars which caused lots of strange build issues. This is really a bummer. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Wilco Greven
commented on JENKINS-13348
EnvInject overriding WORKSPACE variable
I don't think all plugins have already been rebuild with the new EnvInject version.
What we did is creating a job which periodically runs the following Groovy system script:
hudson.EnvVars.masterEnvVars.remove('WORKSPACE')
It's not nice, but it minimizes the damage caused by this bug.
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
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Byron Brummer commented on JENKINS-13348 EnvInject overriding WORKSPACE variable Gregory's patch didn't fix it, the problem still exists. EnvInject 1.87, Jenkins 1.519 Downgrading to 1.36 to work around it. If I get some time I'll walk through releases to narrow down where the problem started. Is it possible to just hardcode 'WORKSPACE' as an untouchable variable? Or perhaps an "Advanced" check box to allow overriding core Jenkins variables of any kind? 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Gregory Boissinot resolved JENKINS-13348 as Fixed EnvInject overriding WORKSPACE variable Change By: Gregory Boissinot (28/May/13 4:15 PM) Status: Reopened Resolved Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
SCM/JIRA link daemon commented on JENKINS-13348 EnvInject overriding WORKSPACE variable Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/envinject/service/EnvVarsResolver.java http://jenkins-ci.org/commit/envinject-lib/ad78b8f1833861e40d4c9d7a56fa7f72ede33bbc Log: Merge pull request #3 from wgreven/JENKINS-13348 Don't overwrite masterEnvVars. Compare: https://github.com/jenkinsci/envinject-lib/compare/1a9def04d4d1...ad78b8f18338 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Wilco Greven commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I can reproduce the issue using Natalia's steps, but not consistently. To check if WORKSPACE has been modified you can check the value of hudson.EnvVars.masterEnvVars using the script console. Could it be that the cause is in EnvVarsResolver.gatherEnvVarsNode? It looks like EnvVars.masterEnvVars is updated directly in that method when the code runs on master. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Natalia Naumova edited a comment on JENKINS-13348 EnvInject overriding WORKSPACE variable Strongly reproduced with scripttrigger plugin jenkins core: 1.492 evinject: 1.82 scripttrigger: 0.26, 0.23 steps to reproduce: JOB1. create any job that polls using scripttrigger plugin with poling node = master JOB2. create job which is restricted to run on master and uses envinject (restart jenkins - looks like it is needed) run JOB2 The results is that $WORKSPACE of JOB2 is defined correctly before envinject, but then it is re-defined with $WORKSPACE of job which use scripttrigger (JOB1). == Started by user ... [EnvInject] - Loading node environment variables. Building on master in workspace /jenkins/jobs/JOB2/workspace [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Executing and processing the following script content: A= [workspace] $ /bin/sh -xe /tmp/hudson5302730654246338218.sh + A= [EnvInject] - Script executed successfully. [workspace] $ /bin/sh -xe /tmp/hudson6529723899012472418.sh + echo /jenkins/jobs/JOB1/workspace /jenkins/jobs/JOB1/workspace Notifying upstream projects of job completion Finished: SUCCESS === Can it be related that envinject and scripttrigger use different envinject-lib ? envinject uses envinject-lib-1.15.jar while scripttrigger uses envinject-lib-1.16.jar ? 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Natalia Naumova reopened JENKINS-13348 EnvInject overriding WORKSPACE variable Strongly reproduced with scripttrigger plugin jenkins core: 1.492 evinject: 1.82 scripttrigger: 0.26, 0.23 steps to reproduce: JOB1. create any job that polls using scripttrigger plugin with poling node = master JOB2. create job which is restricted to run on master and uses envinject (restart jenkins - looks like it is needed) run JOB2 The results is that $WORKSPACE of JOB2 is defined correctly before envinject, but then it is re-defined with $WORKSPACE of job which use scripttrigger (JOB1). == Started by user ... [EnvInject] - Loading node environment variables. Building on master in workspace /jenkins/jobs/JOB2/workspace [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Executing and processing the following script content: A= [workspace] $ /bin/sh -xe /tmp/hudson5302730654246338218.sh + A= [EnvInject] - Script executed successfully. [workspace] $ /bin/sh -xe /tmp/hudson6529723899012472418.sh + echo /u01/jenkins/jobs/JOB1/workspace /u01/jenkins/jobs/JOB1/workspace Notifying upstream projects of job completion Finished: SUCCESS === Can it be related that envinject and scripttrigger use different envinject-lib ? envinject uses envinject-lib-1.15.jar while scripttrigger uses envinject-lib-1.16.jar ? Change By: Natalia Naumova (07/May/13 2:29 PM) Resolution: Cannot Reproduce Status: Closed Reopened 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Byron Brummer commented on JENKINS-13348 EnvInject overriding WORKSPACE variable The issue still exists. Jenkins 1.513, EnvInject 1.85 Same story as the original reporter: Downgrading EnvInject to 1.36 fixes it. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
