That would be preferable if so (in that case you don't want your shell step to error out, yes).
On Tuesday, March 22, 2016 at 2:51:31 PM UTC+11, Andrew Bayer wrote: > > I think the Junit result archiver should mark the build as unstable if > there are failures... > On Mar 21, 2016 7:16 PM, "Michael Neale" <[email protected] > <javascript:>> wrote: > >> I am assuming that ignoring test failures doesn't make the shell step >> fail? (Ie it returns a success code?) >> >> If so, removing that and putting try/catch around it and then the archive >> step in the exception handler along with email could work. There may be a >> better way though (as that seems clumsy) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/8617dfa6-1348-4a16-93c3-eff3dfca871a%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/7a4b99c7-b2b8-46d7-b30d-973da89c5b61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
