Show release candidate builds in the beta crash rate

[philipp-sumo]

During the last week of the beta cycle, one or (usually) more release candidate builds are served to the beta population. Their stability pattern should be reflected in the beta channel's overall crash rate and ideally there is a way to have the rc build broken out as separate version in the graphs section to be able to compare them to the prior beta builds.

[wlach]

@philipp-sumo If the rc builds were/are in buildhub they should appear in mission control (it appears they are not: https://mozilla-services.github.io/buildhub/?channel[0]=beta). I know that we used to have this data in there before I was filtering on buildhub.

I am not entirely sure what the rationale is of having release candidate builds vs. just another beta. Might be worth discussing in the channel and/or cross functional meeting?

[philipp-sumo]

i hope to be able to answer at least the latter part: the rationale there is to provide the identical final build (built off mozilla-release) that has undergone testing by the beta audience to the release channel as well. in the past we have sometimes been plagued by build-specific issues caused by cpu bugs or misbehaving 3rd-party programs hooking into the browser and it's hoped to weed out any such issues this way...

[wlach]

I filed a bug to get metadata from these builds added to buildhub: https://bugzilla.mozilla.org/show_bug.cgi?id=1470948

[wlach]

This is basically waiting on buildhub indexing release candidates on the beta channel. Once that's done mission control will get this feature "for free". See the bug above for more details.

[wlach]

I'm going to move this to relman_v3, as I'd like to close out relman_v2 and I don't know when this will be fixed.

[pascalchevrel]

I see these builds in buildhub: https://mozilla-services.github.io/buildhub/?q=firefox%2067.0&versions[0]=67.0rc2&versions[1]=67.0rc1

And calixte was able to add the crashes in the crash-stop panel on bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1535699

[bhearsum]

I think https://github.com/mozilla-releng/buildhub2/pull/610 will get future builds added to Buildhub. Do we need to backfill these, too?

[bhearsum]

@philipp-sumo - the Buildhub issue is now fixed, and all future mozilla-release builds should also show up on mozilla-beta. Can you verify that this resolves the issue here when we build/ship 71.0?

[philipp-sumo]

will do - thanks for the changes making this possible!

[bhearsum]

71.0 now shows up in Buildhub under the beta channel: https://buildhub.moz.tools/?versions[0]=71.0&channel[0]=beta