When a bug is starred in tbpl, we'd like tbpl to send an XHR request to the orange factor database (see https://wiki.mozilla.org/Auto-tools/Projects/WarOnOrange), to record this data. The request should contain enough information that the bug can be tied to a specific buildbot log; this will be possible once bug 617368 is in production.

(In reply to comment #0) > The request should contain enough information that the bug can be tied to a > specific buildbot log; this will be possible once bug 617368 is in production. It already is!

>> The request should contain enough information that the bug can be tied to a >> specific buildbot log; this will be possible once bug 617368 is in production. > It already is! I see that, thanks!

This patch updates _postOneComment() in tbpl to additionally post some data to a php page hosted by the automation team which will send the data to an elastic search database that is being used for the 'war on orange' project. This database will help us associate starred bug numbers with data scraped from buildbot logs. It tests ok locally; there are some firewall issues which prevent it from running properly in production at the moment (it will just fail silently), filed as bug 618170.

Comment on attachment 496683 [details] [diff] [review] tinderboxpushlog patch diff --git a/js/AddCommentUI.js b/js/AddCommentUI.js _postOneComment: function AddCommentUI__postOneComment(email, comment, machineResult, callback) { + if (comment.toLowerCase().indexOf("bug") > -1) { + machinename = ""; Missing a "var" here.

Btw, the firewall problem has been resolved and this tests OK now.

I've updated the server.