https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1141 Lustre <p>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.</p> <p>A single message consisting of one line (a few lines at most) with a URL to a summary page would be acceptable.</p> LU-1141

Need to take spam reduction measures for Build Master

Bug Minor Resolved Fixed Peter Jones Christopher Morrone Fri, 24 Feb 2012 20:56:54 +0000 Fri, 13 Jul 2012 16:11:02 +0000 Fri, 13 Jul 2012 15:13:52 +0000 1 2 <p>Chris</p> <p>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</p> <p>HTH</p> <p>Peter</p> <p>Peter</p> <p>A closely related problem is that the "spam" that is being posted to Jira is largely useless. The message is of the format (from <a href="https://jira.whamcloud.com/browse/LU-1028" title="Bus error (core dumped) during fsx test" class="issue-link" data-issue-key="LU-1028"><del>LU-1028</del></a> as an example, with the URL expanded):</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>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&amp;a=commit&amp;h=0204171fd3e1b393c53bd374aff228e80080a55a Files : * lustre/osc/osc_request.c </pre> </div></div> <p>but using this URL doesn't actually show anything related to this commit. Doing some quick searching shows that a better URL would be <a href="http://git.whamcloud.com/gitweb?p=fs/lustre-release.git;a=commit;h=0204171fd3e1b393c53bd374aff228e80080a55a" class="external-link" target="_blank" rel="nofollow noopener">http://git.whamcloud.com/gitweb?p=fs/lustre-release.git;a=commit;h=0204171fd3e1b393c53bd374aff228e80080a55a</a>, which links to the "commit" instead of to the "shortlog" (which just shows the full list of all patches applied to the tree).</p> <p>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: <a href="http://git.whamcloud.com/gitweb?p=fs%2Flustre-release.git&amp;a=search&amp;h=HEAD&amp;st=commit&amp;s=I50791554807dddfafafcd2b8d228958ebfa3ac16" class="external-link" target="_blank" rel="nofollow noopener">http://git.whamcloud.com/gitweb?p=fs%2Flustre-release.git&amp;a=search&amp;h=HEAD&amp;st=commit&amp;s=I50791554807dddfafafcd2b8d228958ebfa3ac16</a>.</p> <p>Yes, it is the long streams of jira entries that are bothering me. I filtered the email from Build Master long ago.</p> <p>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.</p> <p>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.</p> <p>The messages from Gerrit patch landing to Jira have been disabled for a month or more.</p> <p>Yes, its been much nicer, thanks!</p> Development Rank 1|hzvh9j: Rank (Obsolete) 6446 Severity