1060649 - Store the build directory as a property on the job, rather than deriving it from the log URL

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder: Data Ingestion, defect, P5)

Description

[Gautam Akiwate [:gakiwate]]

Titanic (https://github.com/gakiwate/titanic/) is a tool to bisect test failures.

Titanic takes revision under investigation - which can be supplied to it using the APIs or command line and then works by pulling data about the revision and revisions before it from TBPL(https://tbpl.mozilla.org/) to bisect the failure.

Titanic needs to trigger of jobs for which it needs the links to the builds for particular platforms etc. At present, this is available in TBPL via a very circumventous route. We query TBPL using getRevisionsBuild and use the 'log' entry to get the build directory.

For example we get the following log path entry for buildername "Android 2.3 mozilla-inbound build" log": "http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/mozilla-inbound-android/1408368977/mozilla-inbound-android-bm91-build1-build23.txt.gz"

Using this we can figure out that the build is in the directory "http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/mozilla-inbound-android/1408368977/"

It would be very helpful if there was a way one could query Treeherder with a revision and buildername and get the equivalent build directory.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

armen, can you see how we are getting the build directory for mozci and ensure we are doing it smart.  Otherwise, we should adapt this bug to be for mozci.

Comment 2

[Armen [:armenzg]]

I grab it from a property.

Comment 3

[Ed Morley [:emorley]]

We still want this for treeherder.

Comment 4

[David Burns :automatedtester]

There isnt a build directory concept in the S3 world so closing as wont fix