1869892 - Remove target.json

Status: NEW

(Release Engineering :: General, task)

Description

[Mike Hommey [:glandium]]

target.json was added in bug 839298 seemingly for socorro, but socorro uses buildhub.json. Chances are everything else that might need the data that target.json contains actually already uses buildhub.json.

I'm not going to take too many risks so close to a freeze, though, but I still want to fix bug 1869078, so as a first step, I'm going to remove a few fields that are probably unused.

Comment 1

[Mike Hommey [:glandium]]

Attachment: Bug 1869892 - Remove *_{cpu,os,vendor} from target.json.

This is a (probably) safe thing to do before going all the way to
removing the file. This will unlock fixing bug 1869078.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/81b5a59aeac7
Remove *_{cpu,os,vendor} from target.json. r=releng-reviewers,bhearsum

Comment 3

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/81b5a59aeac7

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The leave-open keyword is there and there is no activity for 6 months.
:glandium, maybe it's time to close this bug?
For more information, please visit BugBot documentation.

Comment 5

[Mike Hommey [:glandium]]

build_sm.sh says fuzzing is using target.json. Is that true?

Comment 6

[Jason Kratzer [:jkratzer]]

Yes. We use it to get the revision for those builds.

Comment 7

[Mike Hommey [:glandium]]

Could you switch to using buildhub.json, which contains that information?

Comment 8

[Jason Kratzer [:jkratzer]]

Yes but it would need to also be added to the "sm-" prefixed spidermonkey builds. I believe that most of the metadata files for these builds are generated manually.