-
New Feature
-
Resolution: Fixed
-
Major
-
None
It would be great if this plugin could add support for the Claim Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin, 1800 installations).
I imagine two additional features shown to the user in the Project configuration, if the Claim Plugin is installed:
- A "recipient group" called "Claimer" or something so that we can select when this person gets an email.
- One or more triggers related to a failed build which is already claimed. Maybe it could be a checkbox to the existing triggers ("...and is already claimed")
The end result would be that the user can configure that for example only the owners and the claimer (i.e. not the other culprits) will be emailed when a build with a sticky Claim fails again.
- duplicates
-
JENKINS-11638 When claimed, stop sending e-mails to individuals who broke the build
-
- Open
-
- is related to
-
JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object
-
- Resolved
-
-
JENKINS-8202 Smarter broken build email notification
-
- Resolved
-
I don't think the Claim Plugin exports any variables, but I don't know. I've seen the claim status in the builds' APIs.
What I'm looking for is a possibility to make Jenkins not send "build is still failing" e-mails to all committers if a user has Claimed the failing build. Only the claimer (and maybe the default recipients) should get e-mails if the build is claimed. But if no-one has claimed the failing build, then all committers should get emails as normal. Therefore I don't think it would help to add a variable to the recipient list, if such a variable is exported by the Claim Plugin.
I was also considering the custom script that can execute before e-mailing. But this can only stop all e-mails (cancel=true), not modify the recipients list (I think?). I would like it to send e-mails to different recipients depending on the claim status.
The end result and goal is less spam. I think this would fit nicely in email-ext, since I can select who'll get emails when (1st fail, next fails etc). It only needs a "if claimed" option to the triggers and the ability to fetch the claimer's username from the job's API.