|
||||||||
|
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 would volunteer to implement this as a native feature of the plugin to keep it consistent with the existing trigger configuration, but just having a simple checkbox to activate this feature. I see the following options with decreasing preference.
Add a new "Send to Upstream Committers"
Main benefit is that it doesn't change existing functionality and is the most flexible one with regards to configuration
Change behaviour of "Send To Culprits"
You can say that when a build is triggered by a SCM change in a upstream build the committer(s) of the upstream build(s) might be the culprit(s). Drawback is that this changes the current behaviour.
Change behaviour of "Send to Requester"
You can say that when a build is triggered by a SCM change in a upstream build the committer(s) of the upstream build(s) might be the requester(s) although only implicitly. Drawback is the same as option 2 that this changes the current behaviour.
I have the implementation actually available, so I would like to hear your opinion which option you prefer.