Ok, I understand the problem now. The list of authors is pulled from the
change sets for the build. You could create your own recipient provider
plugin, it is an extension point.
On Wed, Jun 1, 2016 at 8:50 AM Mike Lehan wrote:
> Sadly not; the developers list will email
Sadly not; the developers list will email everyone with a commit made in
the current branch. Thus if the developer has recently merged in master and
then pushes, everyone who committed into the most recent diff between their
working copy and master will receive an email, when they don't care
The developers list should work for this, it is what I use with git.
On Wed, Jun 1, 2016, 05:11 Mike Lehan wrote:
> I spent a long time searching for a way to have Jenkins email whichever
> user pushed a branch (on BitBucket) with the notification of how the build
> for
I spent a long time searching for a way to have Jenkins email whichever
user pushed a branch (on BitBucket) with the notification of how the build
for that branch progressed. I wasn't able to find anything so wrote my own
solution and documented it on Stack Overflow.