Hi Jennifer, I'll test out the restarting master node in on Thursday and post the results... but I feel that Simon and I are having the same issue here.
Thanks for the quick replies! VJ On Tuesday, April 28, 2015 at 2:56:23 AM UTC-7, Jennifer Hofmeister wrote: > > Hi VJ, > Hi Simon, > > Just to sum it up… whatever process runs as a service will only load new > env values when restarted. 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 it can pick up new values and pass them on. > It’s all about to which Windows service your node goes back to. (ok, you > said you already tried this… but just to double-check.) > > For me (Windows master and slaves), this was always a safe way to fix env > problems, but if you’re concrete sure it’s no service configuration thing > and still have troubles, maybe try out the “Environment variables” tickbox > in the node configuration. You can have global values overwritten by > whatever you specify, and these variables are then passed on to every > process in the build. > > Best, > > Jennifer > > > -----Original Message----- > From: [email protected] <javascript:> [mailto: > [email protected] <javascript:>] On Behalf Of Simon Richter > Sent: Montag, 27. April 2015 22:44 > To: [email protected] <javascript:> > 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 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 same (all variables, not just PATH). > > It appears that new variables are taken over once when the slave starts, > but then remain at their first value when changed later on. > > Simon > > -- > 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/553E9F81.7010603%40hogyros.de. > > > For more options, visit https://groups.google.com/d/optout. > > > From: Varun Jain [mailto:[email protected] <javascript:>] > Sent: Montag, 27. April 2015 20:17 > To: [email protected] <javascript:> > Cc: Jennifer Hofmeister > Subject: 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 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: [email protected] [mailto:[email protected]] On > Behalf Of Varun Jain > Sent: Samstag, 25. April 2015 00:41 > To: [email protected] > Subject: Jenkins 1.607 - Environment Variables Stuck > > Hey everyone. > > I'm facing an issue where the environment variables seem stuck and > un-updating when running tasks via Jenkins on Windows Slaves. Here are the > steps I do to reproduce, and resolve the problem > 1. Create new Node and set JUST the home directory > 2. Run job with just "echo %PATH%" > 3. Modify PATH, restart Jenkins Slave > 4. Echo PATH via command line, outputs as the correct NEW Path > 5. Run job with jenkins. OLD path is output > > Resolution: > Delete and recreate slave > > Thanks, > VJ > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/3153e714-ee64-490c-b65e-c31812e76864%40googlegroups.com. > > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/52130dfb-3257-4029-9592-84e5e9b754a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
