[JIRA] [envinject-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title Andrew Barber commented on JENKINS-13348 Re: EnvInject overriding WORKSPACE variable I should also note that the job affected by this does not have "Prepare an environment for the run" selected. EnvInject is still lurking though as this message is always present in stdout: [EnvInject] - Loading node environment variables. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title Andrew Barber commented on JENKINS-13348 Re: EnvInject overriding WORKSPACE variable I see this issue as well. EnvInject 1.92.1, jenkins 1.642.1. I originally posted this bug https://issues.jenkins-ci.org/browse/JENKINS-19754 The work around to get WORKSPACE set correctly is to ○ Select "Prepare jobs environment" on the slave ○ Select "Unset System Environment Variables" on the slave After recent upgrades on jenkins and plugins I now see intermittent env inject of WORKSPACE to the slave root. I think the "unset system environment variables" is being ignored intermittently. Passing builds have a small set of environment variables set which appear to be only jenkins related. Failing builds have many more environment variables, especially system ones like HOST and LSF environment variables. The passing cases do not have WORKSPACE set. This is causing a lot of grief for our work. I hope someone can look into it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title
Laurent TOURREAU edited a comment on JENKINS-13348
Re: EnvInject overriding WORKSPACE variable
I have installed 1.92.1 the problem is present.I have downgraded until {color:red}1.38{color} which is the latest version that doesn't have this defect.Here a log extract:{code}Building remotely on quality in workspace /apps/homes/jenkins/node_quality/workspace/sonar_build[sonar_build] $ /bin/sh -xe /tmp/hudson4867033689412661438.sh+ echo now Launching the build workspace...now Launching the build workspace...+ /apps/tools/misc-tools/build_test.shWORKSPACE=/apps/tools/homes/jenkins -calypso /node_quality{code}As you can see WORKSPACE variable is not set correctly
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title Laurent TOURREAU commented on JENKINS-13348 Re: EnvInject overriding WORKSPACE variable I have installed 1.92.1 the problem is present. I have downgraded until 1.38 which is the latest version that doesn't have this defect. Here a log extract: Building remotely on quality in workspace /apps/homes/jenkins/node_quality/workspace/sonar_build [sonar_build] $ /bin/sh -xe /tmp/hudson4867033689412661438.sh + echo now Launching the build workspace... now Launching the build workspace... + /apps/tools/misc-tools/build_test.sh WORKSPACE=/apps/tools/homes/jenkins-calypso/node_quality As you can see WORKSPACE variable is not set correctly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title Martin d'Anjou commented on JENKINS-13348 Re: EnvInject overriding WORKSPACE variable Do you still see the problem with the 1.92.1 released on Aug 21 2015? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
David Rubio commented on JENKINS-13348 EnvInject overriding WORKSPACE variable Same problem detected with EnvInject 1.91.1 and Jenkins 1.609. Version 1.90 does not have the problem 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-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
David Rubio edited a comment on JENKINS-13348 EnvInject overriding WORKSPACE variable Similar problem detected with EnvInject 1.91.1 and Jenkins 1.609. Version 1.90 does not have the problem For some reason the Path env variable is not updated but java.library.path is. When you try to build, it looks in the old path 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.
