1290039 - Add endpoint that delivers all jobs for given revision, including details, notes and bug_job_map

Status: RESOLVED FIXED

(Tree Management :: Treeherder: API, defect)

Description

[Kyle Lahnakoski [:ekyle]]

ActiveData would like to get the details for the jobs related to a particular branch/revision, this includes associated bugs, staring, and taskcluster ids.

This will be used to provide better URLs for various dashboards, and to provide the data necessary to perform cross-comparision between orange factor and ActiveData's test failures list.

Comment 1

[Cameron Dawson [:camd]]

I believe you can do this now with GraphQL.  The GraphQL implementation is a little slow right now, so it depends on how many jobs there are, but feel free to experiment with it:

https://treeherder.mozilla.org/graphql

An example query from the TestGroup UI is:

  query pushesQuery {
    allPushes(revision: "${revision}") {
        edges {
          node {
            id
            revision
            author
            repository {
              name
            }
            jobs (result: "testfailed", tier_Lt: 3) {
              edges {
                node {
                  id
                  result
                  guid
                  tier
                  failureClassification {
                    name
                  }
                  joblogSet {
                    failurelineSet {
                      test
                      subtest
                      message
                      action
                      expected
                      signature
                      group {
                        name
                      }
                    }
                  }
                  jobType {
                    symbol
                    name
                    jobGroup {
                      symbol
                      name
                    }
                  }
                  optionCollectionHash
                  buildPlatform {
                    platform
                    osName
                    architecture
                  }
                }
              }
            }
          }
        }
    }
  }

Comment 2

[Ed Morley [:emorley]]

Just to stress the point that Cameron made above, the graphql endpoint is *very* slow right now, so even only 10% of the activedata load we've seen before would be well into denial of service territory.

Comment 3

[Cameron Dawson [:camd]]

I'm in the final stages of fixing bug 1378473 so that we honor select_related and prefetch_related which should help this.  It DOES require tuning to make sure it includes the fields you need.  

Kyle: I'll do my best to include the fields I think you need during my first phase.  But if I miss any, we can fine-tune it in while fixing this.

Comment 4

[Kyle Lahnakoski [:ekyle]]

This is not needed anymore. The treeherder db mirror is being used.

> {
>     "from":"treeherder",
>     "where":{"and":[{"eq":{"repo.changeset.id12":"21347b456b78"}}]},
>     "limit":10000
> }

https://activedata.allizom.org/tools/query.html#query_id=GlOlm7ys