Closed Bug 688469 Opened 13 years ago Closed 13 years ago

Create the Calendar 1.0b7 release builds

Categories

(Calendar :: Build Config, defect)

Product:
Calendar
Component:
Build Config
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: standard8, Assigned: standard8)

Details

Once I land the patch on bug 685133, I'll be ready to start proper release builds for Lightning.

There's a few config tweaks to do yet, but my plan is to document everything here, and then whoever can take over the production of the builds.

Before we get started I'll need to know that all of Calendar's patches for 1.0b7 have landed in comm-beta. Then I'll need to know the changeset of comm-beta that you want to sign-off against.

For the mozilla-beta changeset, I'd recommend taking the changeset that Thunderbird uses.

Note *-beta will probably become *-release in a few hours as we're merging everything across to the release branch and doing final builds there.
Per Fallen on irc, the remaining changes have now landed. Therefore the following changesets are applicable:

http://hg.mozilla.org/releases/comm-release/rev/0a19c0eb2533
http://hg.mozilla.org/releases/mozilla-release/rev/273977a2c0ea (release branch: GECKO70_2011092208_RELBRANCH)

L10n changesets are the ones for miramar:

http://hg.mozilla.org/build/buildbot-configs/rev/a66944ad1817
* Landed mozconfigs for comm-release as it is new:

http://hg.mozilla.org/build/buildbot-configs/rev/0313c22f2e84

* Landed release configuration and l10n changesets:

http://hg.mozilla.org/build/buildbot-configs/rev/550a096953d2
http://hg.mozilla.org/build/buildbot-configs/rev/48c29a20412d
http://hg.mozilla.org/build/buildbot-configs/rev/1de9384a0100 (typo fix)

* Clobbered builders
* Pulled onto the buildbot master and reconfigured buildbot
* Did the sendchange:

./buildbot.sh sendchange --username=standard8 --master=localhost:9030 --branch=releases/comm-release -m "Lightning 1.0b7 build 1 kick 1" doit

Tagging is now running
On one of the linux boxes:

$ mkdir linuxmerge
$ cd linuxmerge
$ wget http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/linux-i686/lightning.xpi
$ mv lightning.xpi lightning-32.xpi
$ wget http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/linux-x86_64/lightning.xpi
$ mv lightning.xpi lightning-64.xpi
$ mkdir 32 64
$ unzip lightning-32.xpi -d 32
$ unzip lightning-64.xpi -d 64
$ vi 64/install.rdf

Just before the existing em:targetPlatform line, add the line:

<em:targetPlatform>Linux_x86-gcc3</em:targetPlatform>

$ echo binary-component Darwin_x86-gcc3/libcalbasecomps.dylib ABI=Darwin_x86-gcc3 > 64/components/binary.manifest
$ echo binary-component Darwin_x86_64-gcc3/libcalbasecomps.dylib ABI=Darwin_x86_64-gcc3 >> 64/components/binary.manifest
$ mkdir 64/components/Darwin_x86_64-gcc3
$ mv 64/components/libcalbasecomps.so 64/components/Darwin_x86_64-gcc3/
$ mkdir 64/components/Darwin_x86-gcc3
$ mv 32/components/libcalbasecomps.so 64/components/Darwin_x86-gcc3/
$ cd 64
$ zip -r ../lightning.xpi *
$ cd ..
$ ssh -l calbld -i ~/.ssh/calbld_dsa stage.mozilla.org mkdir -p /home/ftp/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/linux && scp -i ~/.ssh/calbld_dsa lightning.xpi calbld@stage.mozilla.org:/home/ftp/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/linux

Then on stage.mozilla.org (as calbld):

$ cd /pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1
$ cp /pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/linux-x86_64/gdata-provider.xpi linux/
$ mkdir source
$ cp /pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/source/sunbird-1.0b7.source.tar.bz2 source/lightning-1.0b7.source.tar.bz2

Hence Linux 1.0b7 builds now up at:

http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/
Previous releases had the binaries in e.g. lightning.xpi\components\Linux_x86-gcc3. 
Linux test build1 has them in lightning.xpi\components\Darwin_x86-gcc3. Does this works?
ahem. Well spotted, I'll fix it now.
Revised Linux Instructions (obsoletes comment 3):

mkdir linuxmerge
$ cd linuxmerge
$ wget http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/linux-i686/lightning.xpi
$ mv lightning.xpi lightning-32.xpi
$ wget http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/linux-x86_64/lightning.xpi
$ mv lightning.xpi lightning-64.xpi
$ mkdir 32 64
$ unzip lightning-32.xpi -d 32
$ unzip lightning-64.xpi -d 64
$ vi 64/install.rdf

Just before the existing em:targetPlatform line, add the line:

<em:targetPlatform>Linux_x86-gcc3</em:targetPlatform>

$ echo binary-component Linux_x86-gcc3/libcalbasecomps.so abi=Linux_x86-gcc3 > 64/components/components.manifest
$ echo binary-component Linux_x86_64-gcc3/libcalbasecomps.so abi=Linux_x86_64-gcc3 >> 64/components/components.manifest
$ mkdir 64/components/Linux_x86_64-gcc3
$ mv 64/components/libcalbasecomps.so 64/components/Linux_x86_64-gcc3/
$ mkdir 64/components/Linux_x86-gcc3
$ mv 32/components/libcalbasecomps.so 64/components/Linux_x86-gcc3/
$ cd 64
$ zip -r ../lightning.xpi *
$ cd ..
$ ssh -l calbld -i ~/.ssh/calbld_dsa stage.mozilla.org mkdir -p /home/ftp/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/linux && scp -i ~/.ssh/calbld_dsa lightning.xpi calbld@stage.mozilla.org:/home/ftp/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/linux

Then on stage.mozilla.org (as calbld):

$ cd /pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1
$ cp /pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/linux-x86_64/gdata-provider.xpi linux/
$ mkdir source
$ cp /pub/mozilla.org/calendar/sunbird/nightly/1.0b7-candidates/build1/source/sunbird-1.0b7.source.tar.bz2 source/lightning-1.0b7.source.tar.bz2

New Linux builds are now up:

http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/
Windows builds got stuck in a different place to expected. We're running commands by hand:

* buildsymbols
* uploadsymbols
* special buildbot command to download all l10n files
* make repack-l10n-all
* make upload

* On stage, created win32 directory in /pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/
* copied lightning.xpi and gdata-provider.xpi from sunbird ... 1.0b7-candidates/build1/unsigned/win32 to the new dir.

Hence Win32 is available there as well now.
Mac failed due to an issue with some of my assumptions around the repack-l10n-all target. Need to think it through, but will probably just do a manual fix up in the morning for now.
Whiteboard: [win32 & linux complete, mac to finish]
Philipp pointed out that we'd not stripped the linux components. I've now done that by downloading onto the builders and doing a strip there, the smaller file is now on the ftp site in the same location (2.8M as opposed to 3.8M). Need to think about how to get that back into build automation.
The mac builds I had to finish manually - the repack-l10n-all script only worked on the non-universal part, so I took that and put the universal stuff into it.

All builds are now available here and I believe they are ready to go:

http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/1.0b7-candidates/build1/

Just need to file some follow-ups before closing this bug.
Whiteboard: [win32 & linux complete, mac to finish] → [need to file follow-ups]
I'm still a bit surprised about the size though. The last Lighting release was 4.8 mb on linux. Assuming each stripped binary component is about 400 kb and the last release contained 4 binary components (32+64 bit / tb5+tb6), 2.7 + 1.6 = 4.3 mb. Where are the missing 500 kb?
I'm not sure, but you could always try extracting the two and doing a recursive diff of the directories (sorry I have to go out now).
I've just been doing the differences and there's nothing obvious in there. I see the last lightning release as about 3M and the current one about 2.8M. The difference there is mainly just the fact we're only shipping one set of binary components.
Filed follow ups: bug 690553, bug 690556, bug 690560
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [need to file follow-ups]
You need to log in before you can comment on or make changes to this bug.