I've started running into problems where a job gets aborted (with a timeout, I think) while in the middle of a database transaction. This left the transaction open, which eventually locked up the database server, causing a bunch of builds to fail. I have a way to shut down stale connections, but need a way to run it when this happens. IIRC, when a job gets aborted, its post-build tasks don't get a chance to run.
Is there a Jenkins idiom for "Run this to clean up after this executor"? Thanks in advance, --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
