628345 - Show Android builds on tbpl front page.

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

I'm not sure what is actually needed to make this happen.

Comment 1

[Aki Sasaki (not active)]

Are you proposing merging the Mobile and Firefox views?

Comment 2

[Jeff Muizelaar [:jrmuizel]]

At least the Android builds, I'm not sure what else is mature enough to be migrated over

Comment 3

[Aki Sasaki (not active)]

I'm fairly sure this will require full developer buy in. Do you want to start a newsgroup thread?

I think this needs to happen at some point, but I'm not sure what that point is, and we need to decide which builds/tests get shown where.

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #2)
> At least the Android builds, I'm not sure what else is mature enough to be
> migrated over

On tbpl, for both mozilla-central and tracemonkey, we already have Android builds displayed. Is that what you were asking for?

Comment 5

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

jrmuizel: (cc-ing stuart for his perspective)

0) Can you confirm that when you say "front page" of tbpl, you mean the "Firefox" branch (aka mozilla-central)? And also that you mean "move from mobile page" not "in addition to the mobile page"? 

1) Turns out the android builds I reported for m-c on tbpl are currently a bug in how tbpl is generated. On m-c, you will only see the gray "B" meaning that an Android build has been queued up. However once the build is completed (green or red), it is removed from m-c and displayed on the mobile page only. 

2) Before we can enable displaying the gray/red/green builds on m-c, all developers using the Firefox tree would need to be ok with Android build bustage closing the m-c tree. Having mobile builds close the tree is something that would need buy-in from both groups before we could flip this switch.

3) The android builds are currently being shown on tracemonkey branch. However, this project branch follows different rules for what does/doesnt close their tree.

4) If we do display Android builds there, I assert that the Maemo builds should be moved to be tracked there also. 

5) There is a separate discussion to be had about how reliable unitests/talos are for Maemo/Android, and I believe these need to be reliable before they could be used to open/close tree.


Hope all that makes sense - its not hard for us to flip those switches but we need to make sure everyone is ok with that first.

Comment 6

[Aki Sasaki (not active)]

https://bugzilla.mozilla.org/show_bug.cgi?id=627604#c8 :

"the decision reached in the public
discussion in m.d.planning was that it wasn't acceptable to have the tip of a
separate repository close mozilla-central, so we were going to wait until
jetpack had something stable that we could import into mozilla-central, and
then have visible tests that ran against that."

This would imply that Android builds, which are dependent on the tip of mobile-browser, should not appear on the Firefox tbpl page.

Comment 7

[Aki Sasaki (not active)]

Choosing the incomplete resolution because I think we want this in the future.

However, without the appropriate discussion and group decision to put mobile builds on the Firefox page, this bug will not proceed further.

Blockers that would solve this:

a) explicit discussion+decision to include Android builds on the Firefox page specifically,
b) a separate discussion+decision to allow non-mozilla-central repositories to close the tree (without specifically mentioning mobile), or
c) merge mobile-browser into mozilla-central.