Closed Bug 608854 Opened 14 years ago Closed 13 years ago

mozharness/scripts/multil10n.py should be fully fleshed out

Categories

(Release Engineering :: General, defect, P5)

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mozilla, Unassigned)

References

Details

(Whiteboard: [mozharness][l10n])

Currently we only use the --pull-locale-source and --add-locales actions to add the multilocale locales to the Android apk.

The script should be able to handle all steps (clobber, pull-build-source, pull-locale-source, build, package-en-US, upload-en-US, add-locales, package-multi, upload-multi) -- I think the packaging and uploading are the ones that I glossed over.

To a lesser degree, there is duplicate code for locale-grokking in signdebs.py and multil10n.py; this can be moved out.

Also, multil10n.py should put its non-Android stuff in one place in lib/, and have an AndroidMultiLocaleScript inherit that and add Android-specific stuff.
Whiteboard: [mozharness]
Whiteboard: [mozharness] → [mozharness][l10n]
Blocks: 651974
In mozharness 0.3 I refactored this, but we still need a fully functioning script that can be run standalone.

Once this is done, we can start moving these builds out of buildbotcustom factories and fully into mozharness scripts.
If I had replaced Android/Maemo builds completely with mozharness scripts, 7.0b5 multilocale builds wouldn't have broken when we stopped cloning buildbot-configs for mozconfigs.
Per the mobile meeting, we will be phasing out multilocale builds in favor of a locale picker.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.