HI Ninad, Thank for the reply. But it doesn't work. Thing is, shell execution works well as part of normal Jenkins job, as a build step. But it fails to work when I add it as workflow step. Not sure if workflow plugin has a different way to invoke shell scripts than traditional Jenkins shell script execution.
Regards, Rupali On Friday, November 28, 2014 3:09:05 PM UTC+5:30, Rupali wrote: > > Hi, > > I tried a simple command in shell script as below: > sh 'echo Hello' > > It gives below error: > > [D:\Jenkins-Slave\workspace\Setup-WF] Running shell script > cygwin warning: > MS-DOS style path detected: > D:\Jenkins-Slave\workspace\Setup-WF\.fb8e6a28\pid > Preferred POSIX equivalent is: > /cygdrive/d/Jenkins-Slave/workspace/Setup-WF/.fb8e6a28/pid > CYGWIN environment variable option "nodosfilewarning" turns off this > warning. > Consult the user's guide for more details about POSIX paths: > http://cygwin.com/cygwin-ug-net/using.html#using-pathnames > sh: D:\Jenkins-Slave\workspace\Setup-WF\.fb8e6a28\script.sh: command not > found > > Can you please advise what could be wrong here? > > Regards, > Rupali > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a0c5a6c2-75e5-432d-a204-9e00cf261042%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
