> Also, I got MinGW running. Only caveat: if the script fails, the .BAT
> still does not fail, hence the result is alway "success". Maybe anyone has
> an idea?

I see Greg has some suggestions, but I wonder if we can get away with something 
really crude here...

What I'm thinking is that:

- Before we invoke sh.exe, the BAT script deletes some marker file

- We invoke sh.exe with the build script

- The build script recreates the marker file on success, just before it returns 
to the BAT script

- the BAT script then checks for the presence of the marker file, and we use 
that test to flag pass/fail to Jenkins...


Well, or some variation on that, where we can create differently named markers 
depending on the exit status (pass, warning, error, etc.) and have the BAT 
script do "something" with ERRORLEVEL on that basis..

Any use?

-- 
Ian






SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 
3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to