Add new endpoint to get bug details as JSON.

dashboard/dashboard/bug_details.py

+# Copyright 2017 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+"""Provides an endpoint for getting details about a sheriffed bug."""
+
+import json
+import re
+
+from dashboard import oauth2_decorator
+from dashboard.common import request_handler
+from dashboard.models import try_job
+from dashboard.services import issue_tracker_service
+
+
+BUGDROID = 'bugdroid1@chromium.org'
+REVIEW_RE = r'Review-Url: (https?:\/\/[\/\.\w\d]+)'
+
+
+class BugDetailsHandler(request_handler.RequestHandler):
+  """Gets details about a sheriffed bug."""
+
+  def post(self):
+    """POST is the same as GET for this endpoint."""
+    self.get()
+
+  @oauth2_decorator.DECORATOR.oauth_required
+  def get(self):
+    """Response handler to get details about a specific bug.
+
+    Request parameters:
+      bug_id: Bug ID number, as a string
+    """
+    bug_id = int(self.request.get('bug_id'), 0)
+    if bug_id <= 0:
+      self.ReportError('Invalid or no bug id specified.')
+      return
+
+    bug_details = self._GetDetailsFromMonorail(bug_id)
+    bug_details['review_urls'] = self._GetLinkedRevisions(
+        bug_details['comments'])
+    bug_details['bisects'] = self._GetBisectsForBug(bug_id)
+    self.response.out.write(json.dumps(bug_details))
+
+  def _GetDetailsFromMonorail(self, bug_id):
+    http = oauth2_decorator.DECORATOR.http()
+    issue_tracker = issue_tracker_service.IssueTrackerService(http)
+    bug_details = issue_tracker.GetIssue(bug_id)
+    bug_details['comments'] = issue_tracker.GetIssueComments(bug_id)
+    return {
+        'comments': bug_details['comments'],
+        'owner': bug_details['owner']['name'],

[sullivan, 2017/02/20 22:48:18]

Note here that I parse out the name so there is some processing here.

I also filter out a lot of the fields that come from the issue tracker, like
there are duplicate 'summary' and 'title' fields.

I think this is clearer than just wholesale copying and forwarding the API data
to the client, WDYT?

+        'published': bug_details['published'],
+        'state': bug_details['state'],
+        'status': bug_details['status'],
+        'summary': bug_details['summary'],
+    }
+
+  def _GetLinkedRevisions(self, comments):
+    """Parses the comments for commits linked by bugdroid."""
+    review_urls = []
+    bugdroid_comments = [c for c in comments if c['author'] == BUGDROID]
+    for comment in bugdroid_comments:
+      m = re.search(REVIEW_RE, comment['content'])
+      if m:
+        review_urls.append(m.group(1))
+    return review_urls
+
+  def _GetBisectsForBug(self, bug_id):
+    bisects = try_job.TryJob.query(try_job.TryJob.bug_id == bug_id).fetch()
+    return [{
+        'status': b.status,
+        'bot': b.bot,
+        'buildbucket_link': '/buildbucket_job_status/%s' % b.buildbucket_job_id,
+        'metric': b.results_data.get('metric'),
+    } for b in bisects]

[sullivan, 2017/02/20 22:48:18]

I realized that it's actually very hard to construct the test path of the
original alert from the try_job entity. The entity doesn't have any fields for
this data, just a results_data with 'metric' and 'command' and a bot, which one
would have to do some serious processing on to reliably get a test path out of.
Perhaps we should store the alert the bisect came from, if there is one?