1181672 - It would be very valuable to have a tool/website that could go from revision to build

Status: RESOLVED WORKSFORME

(Tree Management :: Treeherder: API, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

I.e I have a revision of an inbound build and I want to get a build for it.

Comment 1

[Julien Pagès (:parkouss)]

Well, mozregression can download an inbound build and run it, but it do some bisection to find regressions so there is no way to find "this" build, but more "try builds from this revision to this one".

mozdownload would be appropriate for your use case I think. I don't know if it possible already, but if not it should be in the mozdownload todo list. :)

Comment 2

[Ed Morley [:emorley]]

This is something that sounds like a good candidate for a treeherder api.

Comment 3

[Michael Shal [:mshal]]

Blocking this on bug 1133074. Once we have the index unified, it should be easy to query that for gecko.v1.mozilla-inbound.revision.abc123 or whatever.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Right now the changeset is only supported for tryserver builds in mozdownload. There was a PR (https://github.com/mozilla/mozdownload/pull/94) to get it added for tinderbox builds, but we miss manpower to actually finish it. Meanwhile the code is also outdated, and seeing task cluster coming up soon, I don't think its worth the time to get it implemented right now.

Comment 5

[Julien Pagès (:parkouss)]

Oh, we just added in mozregression the --launch parameter, that allow to download then run a single build given a date (for nightlies) or given a changeset (for inbounds).

Comment 6

[William Lachance (:wlach)]

It would be possible to write this fairly easily using treeherder's current API, for taskcluster builds at least.

Look up result set ids for a revision (in this case a recent mozilla-inbound push):

* https://treeherder.mozilla.org/api/project/mozilla-inbound/resultset/?revision=e7fb74d8faa2

Look up jobs with the right symbol:

* https://treeherder.mozilla.org/api/project/mozilla-inbound/jobs/?result_set_id=184281&job_symbol=B

Find builds (unfortunately using a magic name right now):

* https://treeherder.mozilla.org/api/jobdetail/?job_id=85647230&value=target.tar.bz2

I believe it would also be possible to get the builds for legacy buildbot stuff by truncating the log path (as we do in current treeherder).

All this is to say that I'm not sure that this belongs in Treeherder. Writing a simple UI using github pages might be easier and would let a new contributor work on it (since it would require less specialized knowledge).

Comment 7

[Ed Morley [:emorley]]

This is now possible via the Treeherder API currently, as well as via the Taskcluster index URLs (that allow linking to a specific revision, date or 'latest').