Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored
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? From my understanding, the email generation algorithm mentioned in the wiki is completely separate from the MailAddressResolver which checks the information in the person's account in Jenkins as you said. I could also be completely misinterpreting the doc maybe. On Monday, June 8, 2015 at 8:16:48 PM UTC-7, slide wrote: 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 kna...@gmail.com javascript: wrote: 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 first...@somewhere.com javascript: 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 jenkinsci-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0f1f4a63-33ea-436b-9c7b-4ac4b6407a66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored
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, slide wrote: 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 kna...@gmail.com javascript: wrote: 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 first...@somewhere.com javascript: 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 jenkinsci-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/743e4e70-822e-46fb-9fc2-5579767bcbd4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored
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 first.l...@somewhere.com 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 jenkinsci-users+unsubscr...@googlegroups.com. 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.
Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored
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 knav...@gmail.com wrote: 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 first.l...@somewhere.com 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcUT0kv_6aTbUPEGu7w%2BbAwT%2BxAjkFWRsnadk_UDBknjA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored
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 relevant job settings underneath Editable Email Notifications for Post-build Actions (job*.PNG), and the relevant system configuration settings underneath Extended E-mail Notification (sysconf*.PNG). Does anything seem weirdly off? On Monday, June 8, 2015 at 8:16:48 PM UTC-7, slide wrote: 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 kna...@gmail.com javascript: wrote: 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 first...@somewhere.com javascript: 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 jenkinsci-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b21fb7cf-660e-4c1e-8786-cd8b52048ef6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
