Re: Jenkins 1.607 - Environment Variables Stuck

Deleting slave on master and recreating it helped, so environment stored somewhere on master - and not just path - all environment variables. Master is 1.611 On Thursday, 28 May 2015 18:25:29 UTC+1, Igor Kostenko wrote: > > Hello Everyone, > > I'm installing new jenkins slave on Windows Server 2

Re: Jenkins 1.607 - Environment Variables Stuck

Hello Everyone, I'm installing new jenkins slave on Windows Server 2008 R2 and have exactly the same issue. Previously we were using Windows 7 as windows slaves (master is on linux) and I never had such issue. And I cannot find old path in windows registry, slave hdd and master directory. Have

Re: Jenkins 1.607 - Environment Variables Stuck

Hi Henk, Setting the variable within the Jenkins job works properly (both SET and SETX), but the problem is that when we modify the windows variables (a la button clicking on Windows), restart the slave, the master (restarting the Jenkins client/master and/or rebooting), the environment variabl

Re: Jenkins 1.607 - Environment Variables Stuck

Varun, Have you tried setting the variable with SETX instead of SET ? Henk -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googleg

RE: Jenkins 1.607 - Environment Variables Stuck

s.com [mailto:jenkins...@googlegroups.com] On Behalf Of Simon Richter Sent: Montag, 27. April 2015 22:44 To: jenkins...@googlegroups.com Subject: Re: Jenkins 1.607 - Environment Variables Stuck Hi, On 27.04.2015 14:57, Jennifer Hofmeister wrote: > Does the slave run as a service? If not, it will

Re: Jenkins 1.607 - Environment Variables Stuck

d. > > Best, > > Jennifer > > > -Original Message- > From: jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] On Behalf Of Simon Richter > Sent: Montag, 27. April 2015 22:44 > To: jenkins...@googlegroups.com > Subject: Re: Jenkins 1.60

Re: Jenkins 1.607 - Environment Variables Stuck

Hi Jennifer, > Just to sum it up… whatever process runs as a service will only load new env values when restarted. That is expected behaviour, yes. > The JNLP and JNLP command line options are spawned from the Jenkins master service, so you’ll want to restart that one after changing your envs so

RE: Jenkins 1.607 - Environment Variables Stuck

-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Simon Richter Sent: Montag, 27. April 2015 22:44 To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins 1.607 - Environment Variables Stuck Hi, On 27.04.2015 14:57, Jennifer Hofmeister wrote: > Does the slave run

Re: Jenkins 1.607 - Environment Variables Stuck

Hi, On 27.04.2015 14:57, Jennifer Hofmeister wrote: > Does the slave run as a service? If not, it will probably just read the > Jenkins service’s old PATH in case that one was not restarted after > manipulation. I have the same issue, I can even reboot the slave and the environment stays the s

Re: Jenkins 1.607 - Environment Variables Stuck

Hi Jennifer, I've tried it as the service, the JNLP, and the java command line. All of which yielded the same results. I also did try restarting the service. Thanks, VJ On Monday, April 27, 2015 at 5:57:23 AM UTC-7, Jennifer Hofmeister wrote: > > Hi Varun, > > > > Does the slave run as a ser

RE: Jenkins 1.607 - Environment Variables Stuck

Hi Varun, Does the slave run as a service? If not, it will probably just read the Jenkins service’s old PATH in case that one was not restarted after manipulation. Best, Jennifer From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Varun Jain Sent: Sam