In which mott555 has problems with %PATH%
-
Make sure to count to 15 before turning it back on. Is the green light flickering?
-
Powershell is a scripting language specifically designed to manage servers and such.
I'm not managing servers.
It's like Bash.
Did we forget I was having trouble with Windows 8?
Context. Try some.
Right back at ya.
Discosearch.
Lol.
You're the one who called Powershell a car, and stated that none of the systems you're working with can get the information you need without relying on hacks that interface with DOS compatability.
If you say so.
-
-
I'm not managing servers.
Cool?
Did we forget I was having trouble with Windows 8?
Did you know that my memory lasts longer than two posts?
-
Can you not just run Jenkins as another account? One that will pick up the system
%PATH%
.
-
I assume you tried setx /m?
Okay, so SETX works...something apparently changed between Windows 7 and 8.1, and now SETX does stuff that the bog-standard environment variables dialog and the registry key can't do anymore.
Car vs. unicycle flamewar aside, my current issue is now solved.
-
I wasn't expecting it to work considering what you had tried. It was more of a long shot worth trying.
-
I honestly wasn't even going to try it, because I thought all it did was set the registry key I already tried.
-
-
@mott555 said:
SETX
TIL
Used to be a separate download as part of some admin pack for XP. Not sure if it came with Windows by default in Vista or 7.
setx variable value
sets it locallywhich is probably the same as,set
setx /m variable value
sets it system-wide which isn't possible withset
.Google suggests that since Windows 8 you can even do
setx /s [computer_name]
to do it all remotely. Permissions apply, natch.
-
Oh, I didn't even do
setx /m
, I just usedsetx PATH "%PATH%;my extra paths here"
and it worked
-
Google suggests that since Windows 8 you can even do setx /s [computer_name] to do it all remotely. Permissions apply, natch.
Win7 too. TIL.
-
Yeh - I suspect the "local" bit of
setx
applies to LocalSystem etc - I've never had a need to confirm either way but it working for you suggests it does.
-
Nope it's not flickering, but it's on.... now off.... now onoff.... onoff on off still off on off on fffoo fofnonffonffonf ffonfofofnfonfnofnofnffnoofnf
-
@Magus said:
Pash exists
Petroleum Accountants Society of Houston? Pseudoangiomatous stromal hyperplasia? Some dude from India?
@Muriel Webster's Australian Dictionary said:
Pash : a long passionate kiss;
Filed Under: This port is not empty, Fuck you Discourse
-
-
This one is though:
-
That looks like one of the larger robots ever built.
-
This port is half full
Filed under: Regional Australian Colloquialism Detected
-
MSBuild didn't exist until VS2010...we still do VS2005 and VS2008
-
You know the first thing I thought when I saw this picture? "I wonder what they're hiding behind the wood." It seems to be just leaned against the bottle.
-
I'm going to cry. I had this working on Friday, but now my PATH additions were wiped out and SETX doesn't fix it anymore!
-
I've finally figured out the issue. Unintuitively, if I change the PATH variable on a slave, I have to restart the Jenkins master which is a different PC!!!!! in order for the Jenkins process on the slave to see the changed environment variable.
Front-pagified:
Me: I'm having trouble with my PC.
Tech Support: Have you tried turning it off and back on?
Me: Yes, no effect.
Tech Support: Have you tried turning off and then on this other PC B?
Me: Well no, I'm not having trouble with PC B, it's PC A that's having the issue.
Tech Support: Well turn off PC B and turn it back on, then see if PC A works.
Me: grumbles and complies
Me: That fixed it.
-
Well turn off PC B and turn it back on, then see if PC A works.
I saw that and immediately thought “networking strikes again!”
-
Unintuitively, if I change the PATH variable on a slave, I have to restart the Jenkins master which is a different PC!!!!!
Oh, that'll be because environment variable are cached when you start a process, like the slave's "agent" process. If you had disconnected and reconnected the agent, that would probably have done it as well.
I had the same issue with paths on my bamboo agent just this past week. I wish I'd realized it was the same problem you were having; I just killed the agent shell script and ran it again.
-
Oh, that'll be because environment variable are cached when you start a process, like the slave's "agent" process. If you had disconnected and reconnected the agent, that would probably have done it as well.
Nope. The slave, both its operating system and the slave agent service, had been restarted multiple times. As best as I can tell, the master process caches the slaves' environment variables and forces the slave to use the cached value instead of its actual value, even if the slave disconnects and reconnects for some reason.
-
..Jenkins is weird.