consider for intermittent bug commenter to use a bugzilla account that doesn't send email unless frequent failures
Categories
(Tree Management :: Treeherder, enhancement)
Tracking
(Not tracked)
People
(Reporter: jmaher, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
Treeherder IFV bzcommenter leaves a comment for EVERY bug once/week, and for frequent bugs daily. In thinking about optimizing the workflow, we should consider switching for almost all bzcomments to not email, only email when certain thresholds are crossed.
For example, today we have whiteboard tags [stockwell*] which mean there is an action to take place (like needinfo, disable, retrigger, etc.) Whenever the criteria for one of those is hit, we should send an email- it would be useful to notify related developers.
Also if a bug has > 10% failure rate, this would either be:
- for a given config/variant the test has failed at least 10% of the time
- if the total failures for a bug in the last week are >30 (catch all for most edge cases)
Starting with the stockwell tags and #2 ^, we could reduce emails by 90%+.
:dkl, how realistic is it to get a new bugzilla account which is configured to not send emails when a comment is added to a bug.
Comment 1•2 years ago
|
||
We already have functionality that allows us to maintain a list of bmo accounts that do not trigger email to be sent. We can add any account to this list and whatever changes are made, users will not be notified. The thing that is lacking is it is all or nothing meaning it will skip email for any change, not just comments. We would need to add code to allow some notifications under certain circumstances for specific users. We can definitely do that, even if we just hardcode the account name for now. Creating the account is the easy part.
Comment 3•1 year ago
|
||
Description
•