Unify l10n and l10n-central across Android products
Categories
(Release Engineering :: Release Automation, enhancement)
Tracking
(Not tracked)
People
(Reporter: nalexander, Unassigned)
References
Details
Right now, we root automation checkouts of the l10n repositories for Android products at $topobjdir/../../l10n-central. The l10n repositories for Desktop products are rooted at $topobjdir/../../l10n. This ticket tracks unifying these checkout locations.
Reporter | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
I guess this is automation, mostly? Bouncing around some more.
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Axel Hecht [PTO, back Jan 7][:Pike] from comment #1)
I guess this is automation, mostly? Bouncing around some more.
Yes -- I wasn't clear on where it should live. It fits into the larger "extract l10n setup from mozharness" project.
Comment 3•4 years ago
|
||
Is this still an issue? May be a tc/mozharness config standardization bug if so.
Reporter | ||
Comment 4•4 years ago
|
||
(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #3)
Is this still an issue? May be a tc/mozharness config standardization bug if so.
It's hard to tell, but I think that it's not an issue any longer. In a Desktop L10N(B1) job I see
[task 2020-08-27T11:34:44.945Z] 11:34:44 DEBUG - mkdir_p: /builds/worker/checkouts/l10n-central Already exists.
(See https://firefox-ci-tc.services.mozilla.com/tasks/YCHOFQLdRaeTtw-9KoznQQ.)
Updated•1 month ago
|
Description
•