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}"
}
On Wednesday, May 27, 2015 at 1:07:41 PM UTC-4, LesMikesell wrote:
>
> On Thu, Jan 8, 2015 at 12:35 PM, Jesse Glick <jgl...@cloudbees.com
> <javascript:>> wrote:
> > On Friday, December 5, 2014 6:35:33 AM UTC-5, Rupali wrote:
> >>
> >> So I am concluding that Shell script in in workflow step is not working
> on
> >> Windows slave.
> >
> >
> > Or more precisely, that shell scripts run via durable-task-plugin (this
> also
> > includes the CloudBees Long-Running Build plugin) do not work on at
> least
> > some Cygwin setups. Not surprising, since no one is testing this that I
> know
> > of (only use of the ‘bat’ step), so pull requests are welcome. The
> current
> > assumption is that ‘sh’ is available somewhere in the path, which
> apparently
> > is not true in your case.
>
> I'd go further and say that not much of anything you expect works on
> Cygwin setups. The environment variables that jenkins should export
> to the slaves don't get set in the cygwin environment.
>
> --
> Les Mikesell
> lesmi...@gmail.com <javascript:>
>
--
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/c731e2d7-0b80-4d0c-b3ca-2bbbe13f6ae7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
