Closed Bug 898099 Opened 12 years ago Closed 12 years ago

Switch release_repacks.sh to run on our Windows 64 builders

Categories

(Release Engineering :: Release Automation, defect, P1)

x86_64
Windows Server 2008
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: coop)

References

Details

(Whiteboard: [release][l10n][capacity])

Attachments

(6 files, 1 obsolete file)

We _really_ don't want to support our 32-bit windows builders for another ESR cycle. The only job of substance that still runs on these machines is the release repack builders for mozilla-beta and mozilla-release.
I was hoping this would be fixed by bug 740142...I don't know if it's going to make it in time though...
(In reply to Ben Hearsum [:bhearsum] from comment #1) > I was hoping this would be fixed by bug 740142...I don't know if it's going > to make it in time though... Yeah, me too. In the interim, I've got the release repack builders running in staging and am iterating on the steps to get the mar tools built on win64.
We already build and upload the mar tools for betas, so the first step is change the upload env for release builds to set the tinderbox builds dir (gives us the platform), and then change post_upload.py to put the mar tools in the platform-specific dir for candidates so the repack script can download them instead of building them. We'll still need to run |make configure|, and for that we'll need to start using the in-tree mozconfigs for beta/release. Once we get |make configure| running successfully on win64, the rest of the process should just work (ha!).
Attachment #782069 - Flags: review?(armenzg)
Attachment #782069 - Flags: review?(armenzg) → review+
Attachment #782068 - Flags: review?(armenzg)
Comment on attachment 782069 [details] [diff] [review] Set upload_dir for releases (gives us platform for post_upload.py) https://hg.mozilla.org/build/buildbotcustom/rev/40474423ae55
Attachment #782069 - Flags: checked-in+
Attachment #782068 - Flags: review?(armenzg) → review+
Comment on attachment 782068 [details] [diff] [review] Move mar tools to platform-specific dirs for release candidates https://hg.mozilla.org/build/tools/rev/a039a18a3a38
Attachment #782068 - Flags: checked-in+
Comment on attachment 782068 [details] [diff] [review] Move mar tools to platform-specific dirs for release candidates $ svn ci -m "Bug 898099 - Move mar tools to platform-specific dirs for release candidates - r=armenzg" Sending bin/post_upload.py Transmitting file data . Committed revision 72738.
(In reply to Chris Cooper [:coop] from comment #7) > Comment on attachment 782069 [details] [diff] [review] > Set upload_dir for releases (gives us platform for post_upload.py) > > https://hg.mozilla.org/build/buildbotcustom/rev/40474423ae55 In production.
Attachment #787334 - Flags: review?(aki) → review+
Attachment #786892 - Attachment is obsolete: true
Attachment #787336 - Flags: review?(aki)
Comment on attachment 787336 [details] [diff] [review] Download mar tools from candidates dir, v2 Is this going to bite us on release/esr? I know you've done a lot of testing, but 23.0.1 is around the corner.
Attachment #787336 - Flags: review?(aki) → review+
Comment on attachment 787336 [details] [diff] [review] Download mar tools from candidates dir, v2 Review of attachment 787336 [details] [diff] [review]: ----------------------------------------------------------------- ::: lib/python/build/l10n.py @@ +63,5 @@ > path.join(sourceRepoName, ".mozconfig")) > else: > shutil.copy(mozconfigPath, path.join(sourceRepoName, ".mozconfig")) > + with open(path.join(sourceRepoName, ".mozconfig"), "a") as mozconfig: > + mozconfig.write("ac_add_options --enable-official-branding") This avoids us having to land changes to the l10n-mozconfigs on beta. If we can safely land this l10n-mozconfig change on m-c/aurora/beta/release, we should. @@ +142,5 @@ > env['MBSDIFF'] = mbsdiff > > + log.info("Download mar tools") > + if stageServer: > + if not path.isfile(msys2windows(mar)): All path operations on Windows expect a "E:\builds\..." style path, hence the msys2windows() function. @@ +165,5 @@ > + log.warning('stageServer not set. mar tools will *not* be downloaded.') > + > + compareLocales(compareLocalesRepo, locale, l10nRepoDir, localeSrcDir, > + l10nIni, revision=revision, merge=merge) > + run_cmd(make + ["installers-%s" % locale], cwd=localeSrcDir, env=env) Need to download mar tools before running |make installers|
Attachment #787336 - Flags: review+ → review?(aki)
Comment on attachment 787336 [details] [diff] [review] Download mar tools from candidates dir, v2 resetting flag :)
Attachment #787336 - Flags: review?(aki) → review+
(In reply to Aki Sasaki [:aki] from comment #13) > Comment on attachment 787336 [details] [diff] [review] > Download mar tools from candidates dir, v2 > > Is this going to bite us on release/esr? I know you've done a lot of > testing, but 23.0.1 is around the corner. I haven't done any testing on release or esr yet. Thunderbird is also unknown.
Attachment #787336 - Flags: checked-in+
Attached patch tooltool fixesSplinter Review
Attachment #787699 - Flags: review?(coop)
Attachment #787699 - Flags: review?(coop) → review+
Blocks: 902112
Depends on: 903116
Depends on: 903118
Blocks: 758149
Attached patch tooltool.diffSplinter Review
linux64 for some reason lost one of the changes.
Attachment #788908 - Flags: review?(coop)
Attachment #788908 - Flags: review?(coop) → review+
Product: mozilla.org → Release Engineering
done
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
In production.
Depends on: 915075
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: