Ok, this is weird..it's working now, but I don't really know what I did to
fix it. The MailAddressResolver isn't case sensitive is it? I may have been
modifying my git config user.email around as well as the email address in
the Jenkins "people" list.
On Monday, June 8, 2015 at 8:16:48 PM UTC-7
Hm, if the email-ext gets the email information from a person's information
in the "people" listings (Jenkins users and people mentioned in commit
messages), then what's with the email generation algorithm mentioned in the
wiki? Is that like a second fallback option to resolve the email address?
I'm on Windows 7 x64 Professional and `java -version` gives me:
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
I'm running Jenkins version 1.616, Email Ext is at version 2.40.4. Attached
show the releva
email-ext does use the MailAddressResolver just like Mailer plugin, which
means it should be getting the information from the person's account in
Jenkins. I would need more information about your setup because it works
just fine for me.
On Mon, Jun 8, 2015 at 7:43 PM Kevin Navero wrote:
> I'm cu
I'm currently running into an issue where in my job configuration, the
trigger is set to "Always" and will send an email to the developer of the
last commit after the build is complete. In the logs I get:
Email was triggered for: Always
Sending email for trigger: Always
An attempt to send an e-m
