>
> As I thought - current functionality cannot react to a build result being 
> further updated post-completion. Is there an extension point whereby 
> email-ext can listen for such post-completion events and then rescan 
> (some?) triggers again (ensuring existing completion-triggers ones don't 
> get reactivated)? Does that make sense at all? 

-- 
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.

Reply via email to