Triggers are currently only checked after the build completes. They are not triggers in the sens that they can themselves cause an email to be sent. The email-ext publisher basically loops over all the configured triggers, checks if they are "triggered" and if so sends an email based on the trigger configuration. Hopefully that makes sense.
slide On Thu, Jun 26, 2014 at 4:12 PM, Marc Carter <[email protected]> wrote: > Is it possible (now or feasibly) to write a Trigger for something other > than the direct result of a build. I'm specifically interested in adding > email support to claim-plugin now we have the ability to assign claims to > other people (currently without them knowing) - Claim events *are* > build-related but can happen literally any time. > > It might make things simpler to know that email-ext wouldn't *have* to > listen for anything. With a suitable entry point - claim could directly > invoke the trigger. This isn't very pretty though as it is directly opposed > to how the code appears to handle build results. > > -- Marc > > PS. I hope with the influx of keen new maintainers keeps this great plugin > great! > > -- > 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. > -- Website: http://earl-of-code.com -- 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.
