[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables stuck on windows slave
Title: Message Title William Woodall commented on JENKINS-28278 Re: Environment variables stuck on windows slave Yeah, I totally agree this is a bug or undocumented behavior or both and something should be done. I should have said restarting our master worked around the issue for us too. 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 Nathan Neulinger commented on JENKINS-28278 Re: Environment variables stuck on windows slave Just to be clear though, restart master =~ clear cache and not a permanent fix. 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 William Woodall commented on JENKINS-28278 Re: Environment variables stuck on windows slave I've also run into this. I thought I was going completely crazy. We're using Jenkins ver. 1.611 and Java version 1.7.0_79-b14. We do not have any environment variables set in the config for the master or the slave and the slave is running on Windows. I tried both as a service and from the cmd.exe prompt. We are not using the EnvInject plugin. 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 William Woodall commented on JENKINS-28278 Re: Environment variables stuck on windows slave Restarting our master fixed this issue for me as well. 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 Benjamin Owe commented on JENKINS-28278 Re: Environment variables stuck on windows slave Restarting the master will also do the trick - but a fix is clearly needed. 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'mseeingthissameexactbehaviorbutforRHEL jnlp slaves startedbyascript .Ihavetwoslavesthathavehadthisproblem,andtwothathavenot.Oneoftheslavesthathadthisproblemisonthesamemachinebutrunningasadifferentuserfromtheonethathasnotexperiencedtheissue.Iwoulddisagreethatthisisaminorissue.Wheneverourslavemachinesgetrebooted(orotherwisehaveenvironmentchange)Ihavetomanuallycheckeachslaveandpossiblydelete/recreateit. 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 Nathan Neulinger updated an issue Jenkins / JENKINS-28278 Environment variables stuck on windows slave Change By: Nathan Neulinger Component/s: envinject-plugin 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.
[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables stuck on windows slave
Title: Message Title Nathan Neulinger commented on JENKINS-28278 Re: Environment variables stuck on windows slave Been able to reproduce this several times now. Changes to environment variables are only taking place for a windows jnlp slave if I delete the node and recreate it. Anything else and the vars stick. I've tried completely deleting java cache on slave as well, no effect. Any ideas? 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 Nathan Neulinger created an issue Jenkins / JENKINS-28278 Environment variables stuck on windows slave Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: windows-slaves-plugin Created: 07/May/15 3:59 AM Priority: Minor Reporter: Nathan Neulinger Finally tracked down a really perplexing problem I've been having with some windows slaves. It appears that somehow - the slaves are getting stuck with a particular set of environment variables. No amount of reconfiguration of the windows box - switching user it runs as, running interactively, etc. would change it. The only thing I found that cleared it up is completely deleting the slave from jenkins node list, and re-adding it - then it finally reset what environment variables would be present on the slave. Note - I didn't do ANYTHING other than changing the 'secret' value on the windows box. i.e. I did not reinstall service, relaunch from the nodes list, etc. - just changed the secret that it used to connect with. Is this something obvious that I'm missing in how windows slaves are supposed to behave? Slave is being launched with java web start.
