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
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 2008
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
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
...@googlegroups.comjavascript:
[mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of Simon Richter
Sent: Montag, 27. April 2015 22:44
To: jenkins...@googlegroups.comjavascript:
Subject: Re: Jenkins 1.607 - Environment Variables Stuck
Hi,
On 27.04.2015 14:57, Jennifer Hofmeister wrote:
Does the slave run
...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] On Behalf Of Simon Richter
Sent: Montag, 27. April 2015 22:44
To: jenkins...@googlegroups.com javascript:
Subject: Re: Jenkins 1.607 - Environment Variables Stuck
Hi,
On 27.04.2015 14:57, Jennifer Hofmeister wrote
-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
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
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
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:
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?
11 matches
Mail list logo
