changing it to PATH did the trick, thanks a lot
On Jun 6, 3:51 pm, Slide <[email protected]> wrote: > On Wed, Jun 6, 2012 at 7:41 AM, Pyderman <[email protected]> wrote: > > Hi folks, > > > Looking to set up a job to run a short bash script on a Windows 7 box. > > Cygwin is present and correct. Firstly I had a script with 5 or 6 > > lines, and when called it from the Execute Shell, I was getting > > problems complaining about Windows paths when it was expecting cygwin > > paths. This is now resolved, yet I still get: > > > C:\Users\SERVIC~1\AppData\Local\Temp\hudson8226638213112986683.sh: > > line 2: fg: no job control > > Build step 'Execute shell' marked build as failure > > Finished: FAILURE > > > If I strip the script down to just one simple line such as 'ls -l', or > > even write the line directly in the Execute Shell box thus: > > > set Path=C:\cygwin\bin > > #!/bin/bash > > ls > > > .... I still get the same FAILURE. > > > What is this .sh file that is mentioned above? Does Jenkins take > > whatever is pasted into the Execute Shell box and populate a bash > > script with it?. In either case, I cannot locate this file C:\Users > > \SERVIC~1\AppData\Local\Temp\hudson8226638213112986683.sh to see its > > contentx > > > Many thanks for any advice you can offer. > > FYI, its PATH, not Path. Yes, Jenkins will take the contents of the > build step and create a temporary shell script (which is deleted when > the build step completes) to execute the build step. Is PATH set for > the user that Jenkins is running under (if running as a service, PATH > will need to be set for the user the service is running as). > > slide > > -- > Website: http://earl-of-code.com
