1017529 - Unhide the B2G Flame builds once they meet the visibility requirements

Status: RESOLVED FIXED

(Tree Management Graveyard :: Visibility Requests, defect)

Description

[Ed Morley [:emorley]]

Once bug 1017527 is fixed we can unhide these jobs.

Comment 1

[Jason Smith [:jsmith]]

This is dangerous. Flame builds happen to be the #1 people are reliant on right now for Firefox OS development & testing. Having these builds hidden is a huge risk to causing us to end up with no builds on certain days. There's also no established plan for getting try builds on Flame right now, since the current proposal for try builds requires high overhead & the current reasons to pursue try builds on Flame are nice to haves.

Clint - What do you want to do here?

Comment 2

[Ed Morley [:emorley]]

Other B2G device image builds are still in the default TBPL view, and as such at least some types of breakage will be avoided.

For Flame-specific failures, B2G devs are welcome to use https://tbpl.mozilla.org/?tree=B2g-Inbound&showall=1&jobname=flame to keep an eye on them until they meet the visibility requirements, if that helps?

Comment 3

[Ed Morley [:emorley]]

Note bug 1017527 is where the needinfos are really required, this bug is purely for the TBPL config change.

Comment 4

[Jason Smith [:jsmith]]

(In reply to Ed Morley [:edmorley UTC+0] from comment #3)
> Note bug 1017527 is where the needinfos are really required, this bug is
> purely for the TBPL config change.

Ah right - looks like Clint responded there too, so clearing the needinfo.

Comment 5

[Ryan VanderMeulen [:RyanVM]]

Two months later, Flame builds are generally green and most of the issues brought up in bug 1017527 and this bug have been resolved. Additionally, the primary remaining issue (lack of being able to run them on Try) is common for all device image builds, so it's inconsistent to single-out only Flame for that problem while leaving other device image builds visible by default.

Therefore, after discussion with other sheriffs, we feel that it's best to provisionally un-hide these on trunk. If we find there to be ongoing issues, we will hide them again and reopen this bug. Note that Flame builds were already visible on b2g30 and b2g32, so no change is necessary for v1.4/v2.0.