On Thu, Apr 9, 2020 at 6:51 PM Sarah Clements <scleme...@mozilla.com> wrote:
> Hello, > > As part of maintenance work and performance improvements to Treeherder, > we're making changes to some of the data that's stored in our database. On > *April > 30th*, we will no longer be retrieving uploaded artifacts for jobs and > storing them in the JobDetail table. > > Uploaded artifacts can be retrieved via a taskcluster API, with the > appropriate rootUrl, taskId and runId. TaskId and runId (synonymous with > retryId in Treeherder) can be surfaced from any of our /jobs/ API's. See > this > <https://github.com/mnoorenberghe/mozscreenshots/issues/43#issue-592994567> > for implementation details. > As somebody who has dumped files to MOZ_UPLOAD_DIR and used the job detail tab to download those files (just this week, in fact!), but has only a vague idea of what the "taskcluster API" even is, let alone a "rootURL" or the rest of it, is there any introductory documentation about how I might retrieve files written to MOZ_UPLOAD_DIR? Am I going to have to write some kind of Python script to retrieve my files in the future? That GitHub issue seems to require a lot of background information that I do not have. > We're also planning to deprecate the parsing and storage of TinderboxPrint > log lines in the JobDetail table. They'll no longer be shown in > Treeherder's job detail panel but you can still read them in the raw logs > via the log-viewer. > > If you have any questions or concerns (or need a longer timeline to make > changes that rely on this data), don't hesitate to reach out. > > Sarah > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
