On Wed, May 27, 2015 at 1:39 PM, Boris Chavez-Bravo
<bchave...@squareup.com> wrote:
> I think I have been able to get around this issue by wrapping the call to
> the script through a batch call:
>
> withEnv(["PATH=C:\\cygwin\\bin;%PATH%"]) {
> bat "C:\\cygwin\\bin\\bash ./my_script.sh ${arg1} ${arg2}"
> }
>
I don't mean that cygwin isn't in your path, I mean that if you
configure jenkins to start your slaves via ssh you don't get the
environment settings passed to it that are configured globally or per
node in jenkins on the slaves that are windows with cygwin ssh. Most
of our jobs depend on that to find some tools on a UNC path share so
they fail, where the same node connected some other way would work.
--
Les Mikesell
lesmikes...@gmail.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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAOAgVpy7m4XwJTt18bjkUcnoG%2BqjMpocokCpgtriRKXafiGJgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
