jenkinsci / jenkinsci/git-plugin
[JENKINS-24638] No E-Mail sent when build of new branch fails for first time
- Dominant language
- Java
- Stars
- 694
- Forks
- 1.1k
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 3
Description
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.
---
Originally reported by
kaupo, imported from: No E-Mail sent when build of new branch fails for first time
Raw content of original issue
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: FAILUREThe "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.
- environment:
Email-ext 2.38.1, Jenkins 1.575
Contributor guide
Assessment
This issue has not been assessed yet.