That's odd - I've got jobs that still run the HTML Publisher on failure - are you sure that the HTML file is being put in the same place during a failure scenario?
(Note I'm using a Freestyle job - perhaps if your job type is different then behaviour might change) Richard. On Fri, Aug 9, 2013 at 6:45 AM, Bob Bick <[email protected]> wrote: > Hi,**** > > ** ** > > My Build Flow Plugin based job has a “Publish HTML Report” post-build > action. Regardless of whether the build flow job succeeds or fails, it > generates an HTML report that should be published. Currently, when the > build flow job fails, the HTML file is not published because the job stops > on the failure.**** > > ** ** > > Is there are way to get a post-build action to always execute (even when > there is a failure)? This seems like a very common requirement but I did > not see it documented anywhere. I saw that there is a plugin to run a > script regardless as to whether the job succeeded or failed, but I need the > “Publish HTML Report” post-build action to always run.**** > > ** ** > > Kind Regards,**** > > Bob**** > > > *** *** *** > This message contains information which may be confidential and > privileged. Unless you are the addressee (or authorized to receive for the > addressee), you may not use, copy or disclose to anyone the message or any > information contained in the message. If you have received the message in > error, please advise the sender by reply e-mail and delete the message. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
