Closed
Bug 701113
(maemo-tier3)
Opened 13 years ago
Closed 13 years ago
Maemo -> tier 3
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
References
Details
(Whiteboard: [maemo])
Attachments
(2 files)
33.53 KB,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
80.28 KB,
patch
|
jhford
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
Which means MoCo no longer officially supports it.
Let's link all bugs that we close to this one for tracking.
We need:
* puppet patch to remove scratchbox
* buildbot-configs patch to stop scheduling maemo builds/tests
** remove debtest, mobile from buildbot-configs
* a buildbotcustom followup to remove ScratchboxCommand, any mobiletestfactory stuff
* remove deb signing, maemo multilocale configs/scripts from mozharness
* turn off staging-mobile-master, production-mobile-master
* figure out what to do with the n900s -- these can be useful for someone, and people have asked to purchase them from us
Assignee | ||
Updated•13 years ago
|
Alias: maemo-tier3
Assignee | ||
Updated•13 years ago
|
Depends on: n900-reboots
Assignee | ||
Comment 1•13 years ago
|
||
We need to turn off maemo nightlies before this lands, or we'll get burnination.
Assignee | ||
Comment 2•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
Attachment #573283 -
Flags: review?(jhford)
Comment 3•13 years ago
|
||
Comment on attachment 573283 [details] [diff] [review]
maemo configs
Review of attachment 573283 [details] [diff] [review]:
-----------------------------------------------------------------
I don't think we should be removing the pmm configs quite yet, those n900s can be used for something other than Fennec-Linux-ARM testing.
r+ on everything other than removing the pmm configs.
Attachment #573283 -
Flags: review?(jhford) → review+
Assignee | ||
Comment 4•13 years ago
|
||
Comment on attachment 573283 [details] [diff] [review]
maemo configs
http://hg.mozilla.org/build/buildbot-configs/rev/26d4ff8c15ba
Keeping mobile/ per jhford.
Attachment #573283 -
Flags: checked-in+
Comment 5•13 years ago
|
||
This is now live on the buildbot masters around 12pm PDT.
Assignee | ||
Updated•13 years ago
|
Attachment #573278 -
Flags: review?(rail)
Comment 6•13 years ago
|
||
Comment on attachment 573278 [details] [diff] [review]
remove maemo references in mozharness
The patch looks good but imho it's not complete:
1) need to remove configs/deb_repos directory.
2) The following files in configs/multi_locale contain "locales_file": "build/mobile/locales/maemo-locales":
mozilla-aurora_linux-android.json
mozilla-beta_linux-android.json
mozilla-central_linux-android.json
mozilla-release_linux-android.json
IIRC, we use those configs for dep/nightly builds. Probably we should rename mobile/locales/maemo-locales at some point. This may break the world! :)
Assignee | ||
Comment 7•13 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #6)
> 1) need to remove configs/deb_repos directory.
Easy enough to remove; will do.
> 2) The following files in configs/multi_locale contain "locales_file":
> "build/mobile/locales/maemo-locales":
> mozilla-aurora_linux-android.json
> mozilla-beta_linux-android.json
> mozilla-central_linux-android.json
> mozilla-release_linux-android.json
>
> IIRC, we use those configs for dep/nightly builds. Probably we should rename
> mobile/locales/maemo-locales at some point. This may break the world! :)
It looks like we're turning off multilocale soon, which means maemo-locales will go away entirely. I'd tend towards just letting it die rather than renaming it first, but I'm open.
Updated•13 years ago
|
Attachment #573278 -
Flags: review?(rail) → review+
Assignee | ||
Comment 8•13 years ago
|
||
Comment on attachment 573278 [details] [diff] [review]
remove maemo references in mozharness
http://hg.mozilla.org/build/mozharness/rev/b0f76af66a6e
Attachment #573278 -
Flags: checked-in+
Assignee | ||
Comment 9•13 years ago
|
||
I'm going to call this done. Tracking 2 more bugs.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•