|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I think that in the future I'll make two extension points available
1) Recipient list, which can override the other recipient categories similar to how the triggers can override other triggers. This would make it so that the Claim plugin could implement their own recipient category if they wanted to.
2) I am already working on making the triggers into a better model of the extension point mechanism so that other plugins or code could cause triggers to occur.
I am also adding a ScriptTrigger and PreBuildScriptTrigger so that you could script your own triggers. Would these meet your needs? Basically the idea would be to empower other plugins to implement features like this so that the dependencies of email-ext don't grow exponentially with each plugin that people would like to have support for.