Closed Bug 1518228 Opened 6 years ago Closed 4 years ago

Unify l10n and l10n-central across Android products

Categories

(Release Engineering :: Release Automation, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

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.

Component: General → Localization
OS: Mac OS X → All
Product: GeckoView → Core
Hardware: x86_64 → All

I guess this is automation, mostly? Bouncing around some more.

Component: Localization → Release Automation: L10N
Product: Core → Release Engineering
QA Contact: bugspam.Callek

(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.

Is this still an issue? May be a tc/mozharness config standardization bug if so.

Flags: needinfo?(nalexander)

(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.)

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(nalexander)
Resolution: --- → WORKSFORME
Component: Release Automation: L10N → Release Automation
You need to log in before you can comment on or make changes to this bug.