Hi, IMO, you might need to fix your ant script rather than hacking your build steps, in case you want to hack your jobs look at 1) otherwise see my suggestions 2) which is not a Jenkins question IMO, but I hope it helps.
1) validating build step afterwards using a system groovy step you can access the Jenkins model and query the current build, what I'm not 100% sure whether those previous build steps are already part of the model or still on the fly/memory. There are some examples if you look at the acriptler or post build groovy plugins. 2) ant - errorleves If you use ant can you double check if you trap those errorlevels in the mentioned target? Either using the failonerror attribute or postprocessing those errors in another target via the fail task (as an example) You can also double check when running those steps locally if the errorlevel is non-zero. I hope it helps -- 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/fdb80c5f-eb23-4a4f-b75d-cfa44e5c2f85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
