You are probably running into [1]. I haven't had a chance to look into it yet. Feel free to fork the repo [2] on GitHub and issue a pull request with a patch if you would like to.
slide 1 - https://issues.jenkins-ci.org/browse/JENKINS-2244 2 - https://github.com/jenkinsci/email-ext-plugin/ On Sat, Jul 7, 2012 at 1:18 AM, Miguel Angel Pastor Olivar <miguelinl...@gmail.com> wrote: > Hey guys, > > I would like to ask you about an issue I am suffering since I moved the > email notifications to the mail ext plugin. > > When I configure the plugin, for example, to send an email on every unstable > build to all the committers which make this build unstable I get an email > only for one person, the one who pushed this commit to the master branch. > > Let me give a quickly explanation on how we works (I think as many other > open source projects). All the developers work on their Github repos and > when they are ready the send a pull request (will all the commits) to a > person which acts as a peer reviewer. One the source code satisfies the > requirements, the reviewer push it to the main repo. At this moment only one > person has write permission on the main repo so he is the only one which is > receiving all the emails when a build is failed our unstable. > > I mean, the plugin sees all the commits as done by the person who did the > push to the main repo. > > This is no the behaviour I expected, am I doing something wrong? > > Thx a lot! > > PD: Using the email notifications built-in Jenkins everything was working > fine and all the commiters involved in a build failure receives the email. -- Website: http://earl-of-code.com
