Closed
Bug 1397774
Opened 7 years ago
Closed 7 years ago
Use TC l10n repacks for release
Categories
(Release Engineering :: Release Automation: Other, enhancement, P2)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: mozilla)
References
Details
Attachments
(1 file)
6.85 KB,
patch
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•7 years ago
|
||
I think this should be relatively straightforward once we have bug 1397552: we can then trigger the nightly-l10n, based off the previous graph's build/build-signing/repackage/repackage-signing of en-US.
The downstream tasks (beetmover, balrog, funsize, etc) would then need to depend on the nightly-l10n kind.
We would have to make sure the mozconfigs + mozharness configs we point to are beta / release oriented. That means either pointing at different mozconfigs + mozharness configs, or patching the nightly ones on merge day.
Assignee | ||
Comment 2•7 years ago
|
||
In theory, this will allow us to add l10n tasks to the promotion graph.
This patch depends on bug 1397552 to trigger the promotion graph dependent on the 1st (on-push beta) build graph.
Assignee | ||
Comment 3•7 years ago
|
||
Assignee | ||
Comment 4•7 years ago
|
||
The above patch is landed on date-branch, and other than a typo fix, appears to work well.
Assignee | ||
Comment 5•7 years ago
|
||
We're using tc l10n in fx + devedition + fennec betas. This will ride the trains.
Assignee: nobody → aki
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•