Hello Sarah, others, 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. > > 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. > I have worked with both of these APIs and been frustrated with them (and filed tickets that are now being closed), so I'm pleased to see changes in this area. However, I have some questions. Does the TH UI that exposes artifacts change as part of this? I.e., does it get harder to find the package produced by a build job? I don't see any slated replacement for print lines. A great deal of useful information is summarized in these lines (e.g., we dump libxul/classes.dex/and APK sizes using this mechanism -- or at least we did). What's happening here? Best, Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
