You can configure your job to parse the log looking for strings that mean "failure"; I'm not sure why your job fails then is deemed successful... that seems like a wrapping problem (error codes not being passed up from eclipse/ant to bash to Hudson).
Perhaps Dave's 'run in Ant' [1] instead of 'run in Bash' approach will get around this problem? [1]http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Hudson#ANT_build_Alternative_Configuration If so I'll update the build job template so that everyone can benefit from this better, simpler approach. Nick On Fri, Oct 16, 2009 at 4:08 PM, Gunnar Wagenknecht <gun...@wagenknecht.org> wrote: > Nick Boldt schrieb: >> My fault. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=292476 > > Ah ok, BTW the runPackager stuff works now. However, failed builds show > up as successful in Hudson. Not sure what changed. > > Check this output: > https://build.eclipse.org/hudson/me/my-views/view/Gyrex/job/cbi-gyrex-nightly/20/console > > It says "BUILD FAILED" and down below "Finished: SUCCESS". > > -Gunnar > > > > > -- > Gunnar Wagenknecht > gun...@wagenknecht.org > http://wagenknecht.org/ > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio Release Engineer :: Dash Athena http://nick.divbyzero.com _______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
