Could email-ext be upgraded to also listen to the post-completion build results pages of anything with an email-ext action then rescan triggers appropriately upon change (understanding there's a lot more details involved than this one-liner)? Is that sensible within the existing framework or is it just a no-go?
Put another way - how would you (or anyone else reading this) enable flexible email publication for the claim plugin? -Marc -- 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]. For more options, visit https://groups.google.com/d/optout.
