[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Dmitrii Lapin commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time Same problem on SVN. Is there any provider which can send email to "developer, who created branch"? Sometimes branches can be copied from unstable trunk and developer shoud see results of all builds. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157265.1410250514000.18860.1588077120357%40Atlassian.JIRA.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Vitaly Karasik commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time Daniel - thanks you, got it. So it's not related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Daniel Beck commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time RequesterRecipientProvider' IMHO should "Sends email to the user who initiated the build" exactly as its help says To clarify, requester is the user who clicked "Build Now", not the Git username/email addresses associated with the commits. Is someone manually starting builds and this does not work? If so, that would be a separate bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Vitaly Karasik commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time Agree with Jim - it seems really weird that such important bug with (IMHO) simple fix is still open. I understand that in the first build there is no information about changes, but 'RequesterRecipientProvider' IMHO should "Sends email to the user who initiated the build" exactly as its help says. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Jim Tilander commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time I believe I'm still running into this bug as of today with Jenkins 2.161 and git plugin 3.9.3. Any progress on this issue or is it effectively dead? This pretty much makes culprit emails not work in a PR workflow, and you are forced to email a well known email group instead which is less than ideal. Or have I missed some development? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Stephen Connolly commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time It would be nice if there were metadata from e.g. comparing the branch to master/trunk, but that's SCM specific. Not sure whether SCM API could do that, and whether the email plugins could take that into account. There is the APIs to enable that discovery of changes. We will likely modify the Branch API plugin in the future to provide a link to the branch that a PR is targeting on the changelog... but that may require supporting core changes to handle the fact that a PR's target branch can be changed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title John McGehee edited a comment on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time [~ db danielbeck ], I completely understand your dilemma. I modified my 11 Jan comment to explain the behavior I expected.It is nice to hear from you. I recall fondly our conversations at Jenkins World 2015 and 2016. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title John McGehee commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time David Bottger, I completely understand your dilemma. I modified my 11 Jan comment to explain the behavior I expected. It is nice to hear from you. I recall fondly our conversations at Jenkins World 2015 and 2016. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Alex Earl commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time Git will see the branch and tell email-ext there were no changes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title
John McGehee edited a comment on JENKINS-24638
Re: No E-Mail sent when build of new branch fails for first time
I encountered this same issue with Jenkins 2.19.2, and email-ext 2.52. I did some further experiments, and my results contradict some of the previous comments.I am running {{email-ext}} as described in [Sending Notifications in Pipeline|https://jenkins.io/blog/2016/07/18/pipline-notifications/]. As part of my experiments, I used all the recipient providers I know:{code} def recipients = [[$class: 'CulpritsRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider'], [$class: 'RequesterRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'FailingTestSuspectsRecipientProvider'], [$class: 'FirstFailingBuildSuspectsRecipientProvider']]{code}I tried two scenarios.h3. Push without modificationI started with a branch into which I had purposely introduced a failure. When Jenkins builds this failing branch, it sends a notification email. I created a new branch, and pushed it without modification:{code}git checkout -b notifybuild4git push --set-upstream origin notifybuild4{code}Jenkins built this new branch and failed as expected, but no email was sent, because the providers yielded no recipients:bq. An attempt to send an e-mail to empty list of recipients, ignored.Building branch notifybuild4 a second time resulted in an email being sent. I expected the recipient providers to yield the same email addresses in all these situations:* When the original branch was built (this works)* When branch notifybuild4 was first pushed (this does not work)* When branch notifybuild4 was re-built (this works) h3. Push with modificationStarting with branch notifybuild4 (which fails as described above), I created a new branch, made an immaterial change and and pushed it:{code}git checkout -b notifybuild5atom Jenkinsfile# Add an empty linegit add Jenkinsfile git commitgit push --set-upstream origin notifybuild5{code}Once again, Jenkins' build of this new branch failed as expected, but no email was sent, because the providers yielded no recipients according to the console output from {{email-ext}}:bq. An attempt to send an e-mail to empty list of recipients, ignored.Building branch notifybuild5 a second time resulted in an email being sent. I expected the recipient providers to yield the same email addresses in all these situations: * When branch notifybuild4 was rebuilt (this works)* When branch notifybuild5 was first pushed (this does not work)* When branch notifybuild5 was re-built (this works)
Add Comment
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Daniel Beck commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time I started with a branch into which I had purposely introduced a failure. I created a new branch, and pushed it without modification The idea I mentioned was to create the branch from a master/trunk that builds successfully, so the first build of the branch is identical to master/trunk, and only then introduce changes that could break things. As there's no previous build for the branch, Jenkins has nothing to compare it to to determine who should be emailed. The developer of the last commit? May not be the culprit if there's several changes pushed. Everyone in the history of the branch? Too many false positives. It would be nice if there were metadata from e.g. comparing the branch to master/trunk, but that's SCM specific. Not sure whether SCM API could do that, and whether the email plugins could take that into account. Stephen Connolly? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title John McGehee commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time I encountered this same issue with Jenkins 2.19.2, and email-ext 2.52. I did some further experiments, and my results contradict some of the previous comments. I am running email-ext as described in Sending Notifications in Pipeline. As part of my experiments, I used all the recipient providers I know: def recipients = [[$class: 'CulpritsRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider'], [$class: 'RequesterRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'FailingTestSuspectsRecipientProvider'], [$class: 'FirstFailingBuildSuspectsRecipientProvider']] I tried two scenarios. Push without modification I started with a branch into which I had purposely introduced a failure. I created a new branch, and pushed it without modification: git checkout -b notifybuild4 git push --set-upstream origin notifybuild4 Jenkins built this new branch and failed as expected, but no email was sent, because the providers yielded no recipients: An attempt to send an e-mail to empty list of recipients, ignored. Building branch notifybuild4 a second time resulted in an email being sent. Push with modification Starting with branch notifybuild4 (which fails as described above), I created a new branch, made an immaterial change and and pushed it: git checkout -b notifybuild5 atom Jenkinsfile# Add an empty line git add Jenkinsfile git commit git push --set-upstream origin notifybuild5 Once again, Jenkins' build of this new branch failed as expected, but no email was sent, because the providers yielded no recipients according to the console output from email-ext: An attempt to send an e-mail to empty list of recipients, ignored. Building branch notifybuild5 a second time resulted in an email being sent.
