Currently the bug comments are the easiest way to get to the log - without them, people have to go via Treeherder, filter down to the correct job and open the log that way. We should link to the log in OrangeFactor - there's a "logfile" property already in the ES doc - but Treeherder is currently always populating it with "00000000". Once we make Treeherder give us the actual log URL, we can easily add it to the API response: https://hg.mozilla.org/automation/orangefactor/file/f0b9277fc277/server/handlers.py#l334 ...and then the UI: https://hg.mozilla.org/automation/orangefactor/file/f0b9277fc277/html/scripts/woo.bugs.js#l240 I guess the question now is just whether we link to the raw log, or treeherder's log viewer? The latter has a greater log retention time (albeit just for the error summary excerpt) and highlighting.

Have revised the approach here and in bug 1180052: Treeherder will now provide the job_id, so OrangeFactor can just construct the Treeherder log viewer URL for each failure occurrence. I've also moved the Treeherder single push URL generation to a helper function at the same time, to improve readability. This won't have anything to display until bug 1180052 lands.

https://hg.mozilla.org/automation/orangefactor/rev/1f29368a5a6d (Log links will appear once bug 1180052 is deployed)

Log "View" links now appearing: http://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1147867&startday=2015-07-10&endday=2015-07-11&tree=trunk