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-mail to empty list of recipients, ignored. After reading the wiki, I noticed it says, *Send to Developers * - Check this checkbox to send the email to anyone who checked in code for the last build. The plugin will generate an email address based on the committer's id and an appended "default email suffix" from Jenkins's global configuration page. For instance, if a change was committed by someone with an id "first.last", and the default email suffix is "@somewhere.com", then an email will be sent to "[email protected]" So I tried to change my Jenkins username id to <First>.<Last> and set the default email suffix to a valid email suffix. This still didn't work as I expected. When I use the built-in Jenkins email notifier, I successfully get emails, but only for cases where the build is unstable, and I want the developer who's changes are being tested to receive an email *all the time* after the build is finished. In the Jenkins "People" listing, each committer id is mapped to an email address; does Email Ext not get the email from that, the same way that the built-in Jenkins email notifier does? Worst case scenario, I'll probably end up hacking with Perl and send in the committer email address into the build job as a parameter. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
