No, you need to determine what the username that the scm is returning and
use that.
ira=i...@gmail.com
For a username that is not valid you can add the email address to the
excluded address field in the global config.
On Feb 4, 2014 3:13 AM, "Kamal Ahmed" wrote:
> just to be sure , is this what
just to be sure , is this what i do ?
Lets say:
the incorrect email address formed by emailext is : i...@mail.com
The correct email address should be: i...@mail.com
so in the plugin, global settings, i enter:
i...@mail.com=i...@mail.com
(is that right ?)
also the address : h...@mail.com
is no
There are a couple of things you can do.
1) Use the new mailmap-resolver-plugin to provide a mapping from username
to email address
2) Create user accounts in Jenkins for those users and make sure the email
address is added in their profile
Either of these should do the trick.
slide
On Tue, Ja
Seems that email-ext plugin constructs email by an LDAP user's first initial
and last name and append the @domain (like mail.com) after that.
The problem is that some of these addresses do NOT exist in LDAP and are
bounced, and sometimes go to another unintended person.
How do i resolve this ?
