User:AxelHecht/L10n build tasks
From MozillaWiki
This is a unsorted (the sorted by Sethb) list of things to do for l10n builds.
- build on push
- target response times are currently 5-10 minutes from push to completed build. This replaces bsmedberg's existing setup, but shifts the maintenance to RelEng.
- nightly builds
- Nightly builds should be created following the en-US builds.
- compare locales
- bug 458938 initially. Process for further updates.
- nightly updates
- Nightly updates for l10n builds is the enabler for community testing throughout.
- reliable reporting
- It should be clear from the web interface which builds succeeded and which failed, globally and per locale
- runtime tests
- Runtime tests include Minotaur, but also gathering screenshots from coverage.xpi. Adds build time. Possibly in a scheme like unit tests. More tests to develop.
- l10n merge
- use l10n-merge to create reliable builds, against identified source of the en-US binary in question
make wget-en-US make unpack make ident # update mozilla-central with result from ident here make merge-ab-CD LOCALE_MERGEDIR=$PWD/mergedir make installers-ab-CD LOCALE_MERGEDIR=$PWD/mergedir # upload magic
- keepalive builds
- Tinderbox needs at least one build to show within the last 12 hours or it drops the result. Building every 8 should be safely in that window.