|
||||||||
|
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/d/optout.
This page would be better to understand how to extract upstream developers with a groovy script:
http://stackoverflow.com/questions/14541617/how-can-jenkins-downstream-job-send-email-notification-to-upstream-git-committer
As I mentioned, it's not a bug but a designated behavior of Jenkins.
Parameterized trigger does nothing for that.
If you want both built-in mailer and email-ext extract upstream developers, you can post requests of new features to both of them.