Closed Bug 1420983 Opened 7 years ago Closed 5 years ago

Decide how to store/display uploaded files/artifacts associated with a build

Categories

(Tree Management :: Treeherder, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Unassigned)

References

Details

(Filing this as a new bug, since it's a combination of a number of other older bugs that have more convoluted comment histories.) Back in the days of buildbot/FTP, all artifacts associated with a build (eg logs, binaries, symbols, ...) would get uploaded to the same directory on FTP. This meant that even though TBPL was not provided the URL to this directory by buildbot, it could cheat and trim off the path part of the build log URL, to calculate the "build directory" URL. Treeherder copied this behaviour, making the value of the job details panel "Job name" link to the directory. The kind of use-cases this satisfies are: a) developers who want to download binaries for platforms they don't have locally b) developers who want to be able to paste a URL in a bug to a try push of say a crash fix or debug build for a bug reporter/contributor to try (eg bug 1400904). (In this case they might not know what platform a user is on, so having a generic URL is helpful) However since the buildbot/FTP days: * Many uploads are now to S3, which doesn't allow directory listings / files aren't all uploaded to one place. * Taskcluster is slowly becoming the source of truth so these build directory links are missing from all but the few remaining buildbot jobs. * We now have many "artifact uploaded" type JobDetails (tinderboxprints) that link to assets for a job, on the "Job Details" tab. As such we should decide whether we should just stop ingesting these file names/URLs in Treeherder entirely and instead only link to the taskcluster artifacts inspector [1] (albeit it's perhaps not quite user-friendly enough yet for the "give a link to a contributor" use-case) or else try to reimplement something in Treeherder that works in a Taskcluster world. [1] For example: https://tools.taskcluster.net/index/artifacts/gecko.v2.mozilla-central.revision.948dc86aabc97e16d51ad19ea90debab6f93a628
Maybe we could also pull a list of uploads directly from the taskcluster api endpoint and then display them in the treeherder ui, maybe under a new "Uploads" panel (probably replacing the existing "Job Details" one)? I think being able to download Firefox builds directly from the Treeherder UI would be desirable feature. E.g. for this job: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=444fef22c2010fc5365473fb1200e6766b566270&selectedJob=147887089 You can get a list of artifacts at this url: https://queue.taskcluster.net/v1/task/ViVzUhMGQQ2YoMXLEcJLjQ/runs/0/artifacts I don't think this should be terribly hard to implement.
No longer blocks: 1407665

This is no longer a problem.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Blocks: 1411995
You need to log in before you can comment on or make changes to this bug.