in tbpl we had a field in ouija labeled 'bugid'. This field is the annotations (i.e. 'bug 1234567', 'intermittent' or 'fixed by commint 31415926'). right now we don't have this data from treeherder. Here is an example of a query we call to get information from treeherder: https://treeherder.mozilla.org/api/project/mozilla-inbound/resultset/?format=json&full=true&revision=e573fcf60968&with_jobs=true
it appears I can get the note via this call: https://treeherder.mozilla.org/api/project/mozilla-inbound/note/?job_id=5083195 we need a branch and a jobid, the job id is returned in the resultset. One concern I have is that we will be do one master query for the resultset, then many additional queries for annotations if we have != 'success'
(In reply to Joel Maher (:jmaher) from comment #1) > it appears I can get the note via this call: > https://treeherder.mozilla.org/api/project/mozilla-inbound/note/ > ?job_id=5083195 > > we need a branch and a jobid, the job id is returned in the resultset. > > One concern I have is that we will be do one master query for the resultset, > then many additional queries for annotations if we have != 'success' Mauro, is there an easier way for Joel to get the notes for more than one job at a time?
I think this will only be ~10 calls per job on average, depending on how many failures we have. Having a batch way to do this would be good, otherwise we can work around this :)
It's not possible at the moment, I filed bug 1118212 for it. Please note that there are 2 different endpoints to access the "starring" activity: /api/project/<project_name>/note/ returns the job classifications /api/project/<project_name>/bug-job-map/ returns the bug association So for example if you want to retrieve all the jobs associated to bug 1109932 on mozilla-inbound you can fetch https://treeherder.mozilla.org/api/project/mozilla-inbound/bug-job-map/?bug_id=1109932 I feel we really need to document the api at this point.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.