Closed Bug 1027929 Opened 10 years ago Closed 10 years ago

Use tooltool for l10n builds

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glandium, Assigned: glandium)

References

Details

Attachments

(4 files, 2 obsolete files)

l10n builds should use tooltool on all platforms, using a l10n.manifest file.
The interesting thing is that afaict, release l10n repacks are actually using tooltool (and using the same manifest as normal builds, which is arguably overkill)
release l10n repacks are using tooltool, but they're not running it from the top source directory like other builds, so all assumtions about tooltool tools paths are wrong, which makes release l10n builds not use mozmake despite it being downloaded by tooltool.
Bug 902084 added tooltool to l10n repacks to get mac builds to use clang, but the fact is the builds never actually picked clang from tooltool and the failures must have been fixed some other way. But since I do want l10n builds to use tooltool, might as well do that properly.
Attachment #8443180 - Flags: review?(nthomas)
Assignee: nobody → mh+mozilla
Status: NEW → ASSIGNED
Since l10n repacks never actually used tooltool-downloaded stuff, might as well avoid the overkill-ness of downloading the same things as normal builds and use a different tooltool manifest.
Attachment #8443185 - Flags: review?(nthomas)
Attached patch Add l10n tooltool manifests (obsolete) — Splinter Review
AIUI, android builds use a different config for tooltool.
Attachment #8443191 - Flags: review?(nthomas)
Attachment #8443180 - Attachment is obsolete: true
Attachment #8443180 - Flags: review?(nthomas)
Attachment #8443180 - Attachment is obsolete: false
Attachment #8443180 - Flags: review?(nthomas)
Attachment #8443207 - Flags: review?(nthomas)
After testing on staging, it appears it needed an adjustment for the workdir to be right during repacks.
Attachment #8443276 - Flags: review?(nthomas)
Attachment #8443207 - Attachment is obsolete: true
Attachment #8443207 - Flags: review?(nthomas)
Adding to comm-central configs too.
Attachment #8443278 - Flags: review?(nthomas)
Attachment #8443191 - Attachment is obsolete: true
Attachment #8443191 - Flags: review?(nthomas)
Validated with release l10n repacks and nightly l10n repacks on staging.
Depends on: 1028100
Attachment #8443180 - Flags: review?(nthomas) → review+
Attachment #8443185 - Flags: review?(nthomas) → review+
Attachment #8443276 - Flags: review?(nthomas) → review+
Comment on attachment 8443278 [details] [diff] [review]
Add l10n tooltool manifests

Thanks for taking the effort to test these changes. 

re the earlier conversation about release mac l10n, are you planning to create browser/config/tooltool-manifests/macosx64/l10n.manifest ?
Attachment #8443278 - Flags: review?(nthomas) → review+
(In reply to Nick Thomas [:nthomas] from comment #10)
> Comment on attachment 8443278 [details] [diff] [review]
> Add l10n tooltool manifests
> 
> Thanks for taking the effort to test these changes. 
> 
> re the earlier conversation about release mac l10n, are you planning to
> create browser/config/tooltool-manifests/macosx64/l10n.manifest ?

Considering we're barely building code during l10n, now, and that it works fine with system clang, I'm not convinced it's worth much.
In production
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: