Closed Bug 656912 Opened 13 years ago Closed 13 years ago

The Mobile tree is called "mozilla-central-mobile-browser" in buildbot terms

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mstange, Assigned: mstange)

References

Details

Attachments

(1 file)

Attached patch patchSplinter Review
What was called "tree" in Tinderbox land is called "branch" in Buildbot land. Requesting run information from getRevisionBuilds.php happens with the combination of branch and revision. Currently, the Firefox and Mobile trees have the same primaryRepo and buildbotBranch, so they'd end up identical with the Buildbot backend.
Attachment #532217 - Flags: review?(arpad.borsos)
Comment on attachment 532217 [details] [diff] [review]
patch

Review of attachment 532217 [details] [diff] [review]:
-----------------------------------------------------------------
Attachment #532217 - Flags: review?(arpad.borsos) → review+
OK, this patch isn't landable currently since it would break the self-serve functionality for mobile builds. The self-serve API seems to count all mobile builds to the mozilla-central buildbot branch.
Per bug 656919 comment 3: it would be really awesome if we would have unique bb branches (separation between Firefox and Mobile)
Blocks: 656919
catlee: got an opinion about what we should do here? Since nobody ever looks at Mobile, we now have https://tbpl.mozilla.org/?tree=Mobile which is just tree=Firefox, and https://tbpl.mozilla.org/?tree=Mobile&usetinderbox=1 which is the actual totally unwatched Mobile, where self-serve doesn't work (did self-serve ever actually work for Maemo?). Should we just land this patch, make it show what it should and self-serve be damned?
Oh, I can answer my own question, can't I? Since self-serve only knows about mozilla-central, the branch where the builds live, and not about a mobile or mozilla-central-mobile branch where Maemo tests might live, we *should* expect self-serve to not work.
It's more that the n900's run off a master which is standalone, rather than backed by the schedulerdb, but either way they're not part of self-serve. Aki knows the life expectancy of the n900s.
Correct, https://tbpl.mozilla.org/?tree=Mobile&usetinderbox=1 appears to only be N900s.  The final supported release will be 7.0, which means they will be EOLed by 8.0 (sometime in November?)
Ah, clarity begins to dawn. At some point, there must have been something in the buildbot json which claimed to be on the mozilla-central-mobile-browser branch, but now there isn't: all of Android and the Maemo builds are mozilla-central, and the Maemo tests don't exist in the buildbot json at all.

Altered the Mobile tree's status so it would actually work with tbpl, and added a note saying that if you want to see the Maemo tests, the only point behind loading that tree, you should usetinderbox=1.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: