I finally realized what the problem was. Launching a process does *not* interpolate environment variables in its arguments. The arguments are passed verbatim. It's not the process launching mechanism's job to do so.
It works through cmd.exe because it *is* a command interpreter. I was launching a process for cmd.exe and telling cmd.exe "here's some environment variables", which it then used to execute the process I indicated. But when I launched vault.exe directly, I was launching that executable as a process and telling it "here's some environment variables". But vault.exe doesn't interpolate environment variables. Nor should it. My solution, ultimately, was to pass the password literally, but set it as a 'masked' parameter to Jenkins' ProcStarter. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Launcher-and-environment-variables-on-Windows-tp1008368p4677563.html Sent from the Jenkins users mailing list archive at Nabble.com. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
