-
Bug
-
Resolution: Incomplete
-
Critical
-
None
After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure.
Email was triggered for: Failure - Any Sending email for trigger: Failure - Any An attempt to send an e-mail to empty list of recipients, ignored.
A simplified configuration to recreate the issue is shown below:
- is related to
-
-
- Closed
-
[JENKINS-51090] Emails no longer sent to developers on build failure
Michael Fowler
created issue -
Michael Fowler
made changes -
| Attachment | New: image-2018-05-02-15-34-10-012.png [ 42450 ] |
Michael Fowler
made changes -
| Description |
Original:
After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure. {code:java} Email was triggered for: Failure - Any Sending email for trigger: Failure - Any An attempt to send an e-mail to empty list of recipients, ignored. {code} A simplified configuration to recreate the issue is shown below: !image-2018-05-02-15-28-53-400.png! !image-2018-05-02-15-29-47-973.png! |
New:
After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure. {code:java} Email was triggered for: Failure - Any Sending email for trigger: Failure - Any An attempt to send an e-mail to empty list of recipients, ignored. {code} A simplified configuration to recreate the issue is shown below: !image-2018-05-02-15-28-53-400.png! !image-2018-05-02-15-29-47-973.png! !image-2018-05-02-15-34-10-012.png! |
| Component/s | Original: git-plugin [ 15543 ] |
Reinhold Füreder
added a comment - Just a naive thought/guess:
Is it still not working, or was it "just" this specific build having the problem? If it is the latter, can you check if the "changes" of this specific build may have been empty? If so, then there are no known developers or culprits and thus the log output and not sending any email would be "OK" or at least just a side effect of another problem.
(I stumbled over something like this, when playing around with a sandbox pipeline where I temporarily removed even the SVN checkout step for a test build via pipeline replay; and in the first normal build – i.e. with SVN checkout step again – after this test build, the "changes" were not calculated/shown correctly or IIRC just missing.)
Reinhold Füreder
added a comment - Just a naive thought/guess:
Is it still not working, or was it "just" this specific build having the problem? If it is the latter, can you check if the "changes" of this specific build may have been empty? If so, then there are no known developers or culprits and thus the log output and not sending any email would be "OK" or at least just a side effect of another problem.
(I stumbled over something like this, when playing around with a sandbox pipeline where I temporarily removed even the SVN checkout step for a test build via pipeline replay; and in the first normal build – i.e. with SVN checkout step again – after this test build, the "changes" were not calculated/shown correctly or IIRC just missing.) Reinhold Füreder
added a comment - davidvanlaatum I just stumbled over this unresolved issue here: due to the lack of response of mdkf and/or unlikelihood of this being really a bug and not just caused by possible explanations from my aforementioned comments, I suggest to resolve this issue with something like "Cannot reproduce" or so?
Reinhold Füreder
added a comment - davidvanlaatum I just stumbled over this unresolved issue here: due to the lack of response of mdkf and/or unlikelihood of this being really a bug and not just caused by possible explanations from my aforementioned comments, I suggest to resolve this issue with something like "Cannot reproduce" or so? Possibly linked to this : https://issues.jenkins-ci.org/browse/JENKINS-54940 where BrokenBuildSuspects and Culprits returns an empty list.
Reinhold Füreder
added a comment - duael Thanks for the comment/link: actually in my little (reproducer) project it looks like "BrokenBuildSuspects" is really empty/broken, but "Culprits" is non-empty/correct.
And in the example above "culprits" are used => nonetheless resolve this issue with "cannot reproduce"?
Reinhold Füreder
added a comment - duael Thanks for the comment/link: actually in my little (reproducer) project it looks like "BrokenBuildSuspects" is really empty/broken, but "Culprits" is non-empty/correct.
And in the example above "culprits" are used => nonetheless resolve this issue with "cannot reproduce"? | Link |
New:
This issue is related to |
As far as I know nothing has changed recently that would affect this. Can you turn on debugging in global email-ext settings and post the build output of a failure