Add metadata to all builds pointing to url of symbols/build/tests/etc...

RESOLVED INCOMPLETE

Status

Release Engineering
General
RESOLVED INCOMPLETE
3 years ago
a year ago

People

(Reporter: lightsofapollo, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
(I am sure this is the wrong component)

---

Particularly when running tests out of the tree (gaia/third party etc...) there are times when you want to figure out

 - Where the build came from
 - What type of build it is
 - Where are the symbols (crash reporting)

We have all kinds of "interesting" ways of figuring out this information but it would be nice to have a canonical source of this metadata which we can embed in the builds (the actual things we distribute) at minimum for non-release.
(Reporter)

Comment 1

3 years ago
Can you help me route this? I see a bright future where we can automatically detect symbols (at minimum) and lots of other fun things after we land this... I am planning to prototype this at minimum for TC controlled builds.
(Reporter)

Comment 2

3 years ago
(above comment for mshal)
(Reporter)

Updated

3 years ago
Flags: needinfo?(mshal)
(Reporter)

Comment 3

3 years ago
Some context into what the json would look like (ideally)

{
  "build": "https://queue.taskcluster.net/..../firefox-build.yay.tar.gz",
  "symbols": "https://queue.taskcluster.net/..../symbols.tar.gz",
}
James and I talked about this on IRC a bit, I think the right place for this is to dump an artifacts.json...next to the artifacts. We can stick it in the build archive if that makes people's lives easier. I wouldn't try to shoehorn this into any of our existing files.

We generate other json files that get uploaded in packager.mk:
https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/packager.mk#93

I'd just write a simple Python script that dumps the JSON, like:
https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/informulate.py?from=informulate.py#1

package-name.mk already has all the filenames in Makefile variables:
https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/package-name.mk#124

If you want full URLs obviously you'll need to pass the base URL in from the CI system.
If we're just creating a new file, that definitely simplifies things. I was thinking application.ini or mach_build_properties.json would potentially work here, but they would both need changing.

In order to pass the base URL in, we'll need to tweak mozharness a bit. Right now all of the taskcluster uploading logic happens after the build.
Flags: needinfo?(mshal)
(Reporter)

Updated

3 years ago
Assignee: nobody → jlal
Status: NEW → ASSIGNED
Assignee: jlal → nobody
Status: ASSIGNED → NEW
(Assignee)

Updated

a year ago
Component: Tools → General
Product: Release Engineering → Release Engineering
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.