-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Email-ext 2.38.1, Jenkins 1.575
Steps to reproduce my problem:
1. Using GIT for SCM and Jenkins is set up to trigger build on SCM change
2. Master branch is building fine and all tests are passing
3. Create new branch from master
4. Break something so build fails and push to the new branch
5. Build is triggered in Jenkins by SCM change (but it says "No changes")
Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch. But actually no e-mail is sent and the log says:
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. Finished: FAILURE
The "Failure - Any" trigger has Developers and Culprits set under "Send To". When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail.
[JENKINS-24638] No E-Mail sent when build of new branch fails for first time
Assignee | Original: Alex Earl [ slide_o_mix ] |
Component/s | New: git [ 15543 ] | |
Component/s | Original: email-ext [ 15538 ] |
Labels | Original: email-ext |
Workflow | Original: JNJira [ 157665 ] | New: JNJira + In-Review [ 179641 ] |
Description |
Original:
Steps to reproduce my problem: 1. Using GIT for SCM and Jenkins is set up to trigger build on SCM change 2. Master branch is building fine and all tests are passing 3. Create new branch from master 4. Break something so build fails and push to the new branch 5. Build is triggered in Jenkins by SCM change (but it says "No changes") Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch. But actually no e-mail is sent and the log says: {noformat} 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. Finished: FAILURE {noformat} The "Failure - Any" trigger has Developers and Culprits set under "Send To". When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail. |
New:
translator !chrome-extension://ibppednjgooiepmkgdcoppnmbhmieefh/images/right-arrow.png! * Afrikaans * Albanian - shqipe * Arabic - العربية * Armenian - Հայերէն * Azerbaijani - azərbaycanca * Basque - euskara * Belarusian - беларуская * Bengali - বাংলা * Bulgarian - български * Catalan - català * Chinese - 中文(简体中文) * Chinese - 中文 (繁體中文) * Croatian - hrvatski * Czech - čeština * Danish - dansk * Dutch - Nederlands * English * Esperanto - esperanto * Estonian - eesti * Filipino * Finnish - suomi * French - français * Galician - galego * Georgian - ქართული * German - Deutsch * Greek - Ελληνικά * Gujarati - ગુજરાતી * Haitian Creole - kreyòl ayisyen * Hebrew - עברית * Hindi - हिन्दी * Hungarian - magyar * Icelandic - íslenska * Indonesian - Bahasa Indonesia * Irish - Gaeilge * Italian - italiano * Japanese - 日本語 * Kannada - ಕನ್ನಡ * Korean - 한국어 * Latin - Lingua Latina * Latvian - latviešu * Lithuanian - lietuvių * Macedonian - македонски * Malay - Bahasa Melayu * Maltese - Malti * Norwegian - norsk * Persian - فارسی * Polish - polski * Portuguese - português * Romanian - română * Russian - русский * Serbian - Српски * Slovak - slovenčina * Slovenian - slovenščina * Spanish - español * Swahili - Kiswahili * Swedish - svenska * Tamil - தமிழ் * Telugu - తెలుగు * Thai - ไทย * Turkish - Türkçe * Ukrainian - українська * Urdu - اردو * Vietnamese - Tiếng Việt * Welsh - Cymraeg * Yiddish - יידיש Double-click Select to translate Steps to reproduce my problem: 1. Using GIT for SCM and Jenkins is set up to trigger build on SCM change 2. Master branch is building fine and all tests are passing 3. Create new branch from master 4. Break something so build fails and push to the new branch 5. Build is triggered in Jenkins by SCM change (but it says "No changes") Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch. But actually no e-mail is sent and the log says: {noformat} 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. Finished: FAILURE {noformat} The "Failure - Any" trigger has Developers and Culprits set under "Send To". When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail. |
Description |
Original:
translator !chrome-extension://ibppednjgooiepmkgdcoppnmbhmieefh/images/right-arrow.png! * Afrikaans * Albanian - shqipe * Arabic - العربية * Armenian - Հայերէն * Azerbaijani - azərbaycanca * Basque - euskara * Belarusian - беларуская * Bengali - বাংলা * Bulgarian - български * Catalan - català * Chinese - 中文(简体中文) * Chinese - 中文 (繁體中文) * Croatian - hrvatski * Czech - čeština * Danish - dansk * Dutch - Nederlands * English * Esperanto - esperanto * Estonian - eesti * Filipino * Finnish - suomi * French - français * Galician - galego * Georgian - ქართული * German - Deutsch * Greek - Ελληνικά * Gujarati - ગુજરાતી * Haitian Creole - kreyòl ayisyen * Hebrew - עברית * Hindi - हिन्दी * Hungarian - magyar * Icelandic - íslenska * Indonesian - Bahasa Indonesia * Irish - Gaeilge * Italian - italiano * Japanese - 日本語 * Kannada - ಕನ್ನಡ * Korean - 한국어 * Latin - Lingua Latina * Latvian - latviešu * Lithuanian - lietuvių * Macedonian - македонски * Malay - Bahasa Melayu * Maltese - Malti * Norwegian - norsk * Persian - فارسی * Polish - polski * Portuguese - português * Romanian - română * Russian - русский * Serbian - Српски * Slovak - slovenčina * Slovenian - slovenščina * Spanish - español * Swahili - Kiswahili * Swedish - svenska * Tamil - தமிழ் * Telugu - తెలుగు * Thai - ไทย * Turkish - Türkçe * Ukrainian - українська * Urdu - اردو * Vietnamese - Tiếng Việt * Welsh - Cymraeg * Yiddish - יידיש Double-click Select to translate Steps to reproduce my problem: 1. Using GIT for SCM and Jenkins is set up to trigger build on SCM change 2. Master branch is building fine and all tests are passing 3. Create new branch from master 4. Break something so build fails and push to the new branch 5. Build is triggered in Jenkins by SCM change (but it says "No changes") Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch. But actually no e-mail is sent and the log says: {noformat} 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. Finished: FAILURE {noformat} The "Failure - Any" trigger has Developers and Culprits set under "Send To". When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail. |
New:
Steps to reproduce my problem:
1. Using GIT for SCM and Jenkins is set up to trigger build on SCM change 2. Master branch is building fine and all tests are passing 3. Create new branch from master 4. Break something so build fails and push to the new branch 5. Build is triggered in Jenkins by SCM change (but it says "No changes") Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch. But actually no e-mail is sent and the log says: {noformat} 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. Finished: FAILURE {noformat} The "Failure - Any" trigger has Developers and Culprits set under "Send To". When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail. |