1386970 - l10n mozharness scripts should use mach entry points

Status: NEW

(Release Engineering :: Applications: MozharnessCore, enhancement)

Description

[Axel Hecht [:Pike]]

With bug 1370506, we're having top-level entry points for l10n steps, and less l10n steps.

mozharness should use those:

./mach configure
if not disable-compile-environment:
  ./mach build -C config export
./mach build wget-en-US  # needs an EN_US_BINARY_URL, and target.foo for TC

... the unpack, ident, update m-c if needed stuff doesn't exist on the top-level yet.

./mach build installers-{locale}  # for single-locale builds

... upload and balrog etc is where I compared mobile_l10n.py and desktop_l10n.py, and no idea if those are actually needed to be that different.


For multi-locale, ./mach build chrome-{locale} will work.

There's no need to run compare-locales yourself, nor to specify a merge dir, those will be handled for you once bug 1370506 sticks.

Also, please use the top-level mach targets in particular for chrome-% and installers-%, as they're taking care of running things with make -j, or, right now, not. That way, once we can run parts of repacks with make -j, it'll be faster.
To clarify, I don't think we'll be able to run different locales in parallel with what we're doing these days. chrome-% yes, I guess, but installers-% not.

Comment 1

[Aki Sasaki (not active)]

For fennec, will mach use the in-tree l10n changesets?
For firefox, how are we able to pass in an l10n revision?

Or is this after we clone and update the l10n repos?

Comment 2

[Axel Hecht [:Pike]]

(In reply to Aki Sasaki [:aki] (out Aug3) from comment #1)
> 
> Or is this after we clone and update the l10n repos?

Yes, this is after setup().