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 variables modified on the Jenkins Slave (Windows) are not updated within Jenkins. It's like Jenkins, on first run, snapshots the environment variables and never loads them from the OS again.\
Thanks, VJ On Wednesday, April 29, 2015 at 4:28:36 AM UTC-7, Henk van Voorthuijsen wrote: > > 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b3c6acec-ca58-49ff-869b-150aadec9b61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
