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
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
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
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
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
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
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
-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,
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
ns...@googlegroups.com ] *On Behalf Of *Varun Jain
> *Sent:* Samstag, 25. April 2015 00:41
> *To:* jenkins...@googlegroups.com
> *Subject:* Jenkins 1.607 - Environment Variables Stuck
>
>
>
> Hey everyone.
>
>
>
> I'm facing an issue where the envi
: Samstag, 25. April 2015 00:41
To: jenkinsci-users@googlegroups.com
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
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. M
12 matches
Mail list logo
