[Findit] Adding additional fields to try job metadata

appengine/findit/model/wf_try_job_data.py

Index: appengine/findit/model/wf_try_job_data.py
diff --git a/appengine/findit/model/wf_try_job_data.py b/appengine/findit/model/wf_try_job_data.py
index 96daade5c467a285a48b1b1e67df6ab6b13f51f4..5e963186122042aa28c5c12b1ddc45eb2938de3a 100644
--- a/appengine/findit/model/wf_try_job_data.py
+++ b/appengine/findit/model/wf_try_job_data.py
@@ -11,6 +11,8 @@ class WfTryJobData(ndb.Model):
   master_name = ndb.StringProperty(indexed=True)
   # The original buildername on which the build was detected to have failed.
   builder_name = ndb.StringProperty(indexed=True)
+  # The original build number.
+  build_number = ndb.IntegerProperty(indexed=True)
   # The type of try job, such as 'compile' or 'test'.
   try_job_type = ndb.StringProperty(indexed=True)
   # When the try job was created.
@@ -29,6 +31,8 @@ class WfTryJobData(ndb.Model):
   try_job_url = ndb.StringProperty(indexed=False)
   # Error message and reason, if any.
   error = ndb.JsonProperty(indexed=False)
+  # The last buildbucket build response received.
+  last_buildbucket_response = ndb.JsonProperty(indexed=False)

[stgao, 2016/04/22 00:37:53]

This should be rarely used, let's compress it like others.

[lijeffrey, 2016/04/22 00:50:53]

I'm actually thinking of getting rid of culprits, number of commits analyzed,
regression range size, etc. in a later CL since this field will contain the full
report too which can be used to derive the other information?

[stgao, 2016/04/22 01:06:22]

We could do that for new data. But how do you plan to deal with legacy data?
Drop them?

 
   # TODO(lijeffrey): We may want to determine whether or not a try job
   # was triggered as a redo of another if the first failed to find a culprit.