Two things: 1. We have a Buildhub and a Buildhub2. Buildhub is probably going to get decomissioned once we get Buildhub users moved over to Buildhub2. Buildhub2 is at https://buildhub.moz.tools/ . 2. Having said that, the problem is still the same. Both Buildhub and Buildhub2 (and Socorro) pull their build information from archive.mozilla.org from buildinfo.json files generated during the build process and they're only looking at specific information. Is Fenix information on archive.mozilla.org? I didn't think it was, but maybe I just don't know where it is. For products that use different build/release systems than Firefox, we have a couple of options. One option is the product release systems adds data in the appropriate directories and formats to archive.mozilla.org and then we fix Buildhub2 to slurp that up. The other option is that we add accounts, API tokens, an API to Buildhub2 so that product release systems can push that information into Buildhub2 when the release is done. Off the top of my head, growing an API seems the most flexible, but I haven't really given this much thought. This feels like a multi-month project. I wrote up this issue for it: https://github.com/mozilla-services/buildhub2/issues/542
Bug 1552583 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Two things: First, we have a Buildhub and a Buildhub2. Buildhub is probably going to get decomissioned once we get Buildhub users moved over to Buildhub2. Buildhub2 is at https://buildhub.moz.tools/ . Second, having said that, the problem is still the same. Both Buildhub and Buildhub2 (and Socorro) pull their build information from archive.mozilla.org from buildinfo.json files generated during the build process and they're only looking at specific information. Is Fenix information on archive.mozilla.org? I didn't think it was, but maybe I just don't know where it is. For products that use different build/release systems than Firefox, we have a couple of options. One option is the product release systems adds data in the appropriate directories and formats to archive.mozilla.org and then we fix Buildhub2 to slurp that up. The other option is that we add accounts, API tokens, an API to Buildhub2 so that product release systems can push that information into Buildhub2 when the release is done. Off the top of my head, growing an API seems the most flexible, but I haven't really given this much thought. This feels like a multi-month project. I wrote up this issue for it: https://github.com/mozilla-services/buildhub2/issues/542