[JIRA] [envinject-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Brendan Billingsley commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave I don't have the EnvInject plugin installed. I'm similarly glad someone else has this issue as I was also going a little crazy trying to figure out what was going on. 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] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Brendan Billingsley edited a comment on JENKINS-28278 Re: Environment variables "stuck" on windows slave I'm seeing this same exact behavior but for RHEL jnlp slaves started by a script . I have two slaves that have had this problem, and two that have not. One of the slaves that had this problem is on the same machine but running as a different user from the one that has not experienced the issue.I would disagree that this is a minor issue. Whenever our slave machines get rebooted (or otherwise have environment change) I have to manually check each slave and possibly delete/recreate 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] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Brendan Billingsley commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave I'm seeing this same exact behavior but for RHEL jnlp slaves. I have two slaves that have had this problem, and two that have not. One of the slaves that had this problem is on the same machine but running as a different user from the one that has not experienced the issue. I would disagree that this is a minor issue. Whenever our slave machines get rebooted (or otherwise have environment change) I have to manually check each slave and possibly delete/recreate 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.
