[LU-1141] Need to take spam reduction measures for Build Master Created: 24/Feb/12 Updated: 13/Jul/12 Resolved: 13/Jul/12 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Christopher Morrone | Assignee: | Peter Jones |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 6446 |
| Description |
|
We seriously need to take measures to fix the jira spam from Build Master. It is quite disruptive to have a nice conversation going in a jira ticket only to have it interrupted by 20 entries from Build Master with most repeated information. So I page-down like a maniac only to later find that I skipped over an important little comment smack dab in the middle of two big Build Master spam sessions. A single message consisting of one line (a few lines at most) with a URL to a summary page would be acceptable. |
| Comments |
| Comment by Peter Jones [ 24/Feb/12 ] |
|
Chris I agree that this is a nuisance and we already have an internal test infrastructure ticket to track getting this fixed. IIRC someone has looked into this and we need to upgrade to a newer version of one of the pieces of software (I think gerrit) before this becomes possible. In the meantime I suggest that you make use of a mail filter to siphon off the "spam" into a separate folder. I would think that a rule that checks for sender JIRA and body containing "Build Master commented on" should do the trick HTH Peter Peter |
| Comment by Andreas Dilger [ 27/Feb/12 ] |
|
A closely related problem is that the "spam" that is being posted to Jira is largely useless. The message is of the format (from Integrated in lustre-master ยป x86_64,client,el5,inkernel #479
LU-1028 osc: fix grant checking on the osc side (Revision 0204171fd3e1b393c53bd374aff228e80080a55a)
Result = SUCCESS
Oleg Drokin : 0204171fd3e1b393c53bd374aff228e80080a55a | http://git.whamcloud.com/gitweb?p=fs/lustre-release.git;a=shortlog;h=refs/heads/master&a=commit&h=0204171fd3e1b393c53bd374aff228e80080a55a
Files :
* lustre/osc/osc_request.c
but using this URL doesn't actually show anything related to this commit. Doing some quick searching shows that a better URL would be http://git.whamcloud.com/gitweb?p=fs/lustre-release.git;a=commit;h=0204171fd3e1b393c53bd374aff228e80080a55a, which links to the "commit" instead of to the "shortlog" (which just shows the full list of all patches applied to the tree). It would alternately be possible to link to a search for the "Change-Id:" tag, so that the patch can be found even if it is backed out or landed onto another branch: http://git.whamcloud.com/gitweb?p=fs%2Flustre-release.git&a=search&h=HEAD&st=commit&s=I50791554807dddfafafcd2b8d228958ebfa3ac16. |
| Comment by Christopher Morrone [ 27/Feb/12 ] |
|
Yes, it is the long streams of jira entries that are bothering me. I filtered the email from Build Master long ago. Andreas's points are good too. Although in addition to making the message better, I really want there to be ONE message instead of many for each mass integration event. |
| Comment by Ned Bass [ 14/Mar/12 ] |
|
I might add pollution of the Jira RSS feed as another bothersome aspect of this issue. It will be nice to get this resolved because the RSS feed is otherwise quite handy. |
| Comment by Andreas Dilger [ 13/Jul/12 ] |
|
The messages from Gerrit patch landing to Jira have been disabled for a month or more. |
| Comment by Christopher Morrone [ 13/Jul/12 ] |
|
Yes, its been much nicer, thanks! |