Closed
Bug 849019
Opened 12 years ago
Closed 11 years ago
Do Windows release repacks on Win64
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
x86_64
Windows Server 2008
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: coop, Unassigned)
References
Details
(Whiteboard: [release][l10n][capacity])
Once we can do nightly win32 repacks on Win64 machines (bug 784848), we should port those changes to the release repack script.
Comment 1•12 years ago
|
||
Reading over the patches from bug 784848, it looks like we have to:
* use an objdir
* call make.py instead of make when building nsinstall
* stop building mar tools and download them instead
* switch the l10n_slaves for beta, release, esr17
Need to make sure to test this explicitly for firefox and thunderbird
Coop, does this need to ride the trains at all? Will it even work on esr17?
Updated•12 years ago
|
Flags: needinfo?(coop)
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Ben Hearsum [:bhearsum] from comment #1)
> Reading over the patches from bug 784848, it looks like we have to:
> * use an objdir
> * call make.py instead of make when building nsinstall
> * stop building mar tools and download them instead
> * switch the l10n_slaves for beta, release, esr17
>
> Need to make sure to test this explicitly for firefox and thunderbird
>
> Coop, does this need to ride the trains at all? Will it even work on esr17?
All of the above should work for beta & release. ESR17 probably won't be able to use pymake, but it would be worth trying to see if it could. We can continue setting makeCmd=make there as long as required.
The in-tree build config changes required for this are already in beta, and in a few weeks will make it onto release. The l10n-mozconfig files on beta and release will require some tweaking to fix the --with-l10n-base location to be branch-specific (see bug 852553 for the planned fix).
Once the in-tree l10n-mozconfigs are fixed, we should be able to switch both beta & release in one go anytime after Firefox 20 is released, i.e. the build config changes currently on mozilla-beta are merged into mozilla-release.
Flags: needinfo?(coop)
Comment 3•12 years ago
|
||
OK, we should skip ESR17 then. Relevant code for the required changes is:
https://github.com/mozilla/build-tools/blob/master/scripts/l10n/create-release-repacks.py
https://github.com/mozilla/build-tools/blob/master/lib/python/build/l10n.py#L47
Comment 4•11 years ago
|
||
bug 740142 is getting some work, which will move desktop Firefox repacks to mozharness. Once that's done for nightly + release builds, we get this for free. Leaving open for now though.
Comment 5•11 years ago
|
||
We don't have an exact timeline yet, but bug 740142 *is* going to happen. There's no point in adjusting the old scripts now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•