You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is feasible in Buildhub, but our telemetry shows that we have users with BuildID 20240916093609 which corresponds to 130.0.1 and seems to be our snap build.
This is a different Build ID than what we ship for all platforms (including our own .deb), which is 20240913135723 and BuildHub doesn't know about it.
Given that snap is the default to Ubuntu, this skews a bit the results of Pollbot for the uptake %.
Ideally, we would use in our snap build the same buildID that we use for our other official packages so the BuildHub and PollBot APIs would give the correct information in their API.
But maybe there is a data source BuildHub could use to know about the snap buildIDs ?
The text was updated successfully, but these errors were encountered:
I don't know if this is feasible in Buildhub, but our telemetry shows that we have users with BuildID 20240916093609 which corresponds to 130.0.1 and seems to be our snap build.
This is a different Build ID than what we ship for all platforms (including our own .deb), which is 20240913135723 and BuildHub doesn't know about it.
Given that snap is the default to Ubuntu, this skews a bit the results of Pollbot for the uptake %.
https://pollbot.services.mozilla.com/v1/firefox/130.0.1/telemetry/main-summary-uptake
Ideally, we would use in our snap build the same buildID that we use for our other official packages so the BuildHub and PollBot APIs would give the correct information in their API.
But maybe there is a data source BuildHub could use to know about the snap buildIDs ?
The text was updated successfully, but these errors were encountered: