Hi Jorge, Kohsuke,
Now I am getting a different error as below:
[D:\Jenkins\jobs\BUILD-DEPLOY-TEST-CERTIFY-WF\workspace] Running shell script
cygwin warning:
MS-DOS style path detected:
D:\Jenkins\jobs\BUILD-DEPLOY-TEST-CERTIFY-WF\workspace\.dddf1bf9\pid
Preferred POSIX equivalent is:
/cygd
Thanks. Both of you are right.
I missed checking configuration on Slave.
Corrected it now and its working fine.
Regards,
Rupali
On Wednesday, November 26, 2014 5:53:49 PM UTC+5:30, Rupali wrote:
>
> I am trying to run a shell script on Windows Server.
> Usually we set start line in shell script a
I agree wth Jorge, it looks like your PATH is incomplete. Are you sure it's
in the system "Path" variable? You can check the system info page on the
slave in question to see if Jenkins slave process is correctly inheriting
it. Maybe you changed the env variable after you launched the slave --- the
Make sure that when the slave starts it has the path of all the cygwin
binaries (path to nohup.exe)
On Wednesday, November 26, 2014 1:23:49 PM UTC+1, Rupali wrote:
>
> I am trying to run a shell script on Windows Server.
> Usually we set start line in shell script as "#!d:\cygwin\bin\bash.exe -l"
I am trying to run a shell script on Windows Server.
Usually we set start line in shell script as "#!d:\cygwin\bin\bash.exe -l"
to point to bash under cygwin.
This is not working in work-flow step.
*I have written shell script execution step as below:*
sh '''#!d:\\cygwin\\bin\\bash.exe -l
cd $WOR
