SeaMonkey:Release Process:2.5

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.5

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 703904

Build Engineer

Justin Wood

Signed-off Revisions

releases/comm-release
 727595a78622
releases/mozilla-release
 FIREFOX_8_0_1_BUILD2
(GECKO80_2011110416_RELBRANCH)
dom-inspector
 b075d299d443
(DOMI_2_0_10)
chatzilla
 SEA_2_5_BASE
venkman
 65b690f78f60

L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it).

Notes

  • Have to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that
  • Release is a bit late due to the machine failure and Firefox 8.0.1

Build

  • Made sure all build machines have clean release directories.
    • Used clobberer
  • Updated build/buildbot-configs 193e14384acf for l10n and configs
  • Updated build/buildbot-configs 5dd00b56cbf1 to move symlink
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
bin/buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.5build1" doit
  • Tagging failed for locale 'be' and aborted
    • Was due to be missing the cset that we used on -release. I ran a local shell script to push our relbranch for 2.5b4 to their release repos, so that we can be sure every locale has necessary csets.
  • Retriggered with the following command.
bin/buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.5build1" doit
  • Tagging failed again, due to specifying to bump the version, and "no changes".
    • Fixed that in repo
    • locally edited ReleaseTaggingFactory to specify the relbranch as SEA_COMM801_20111120_RELBRANCH since we passed the date line to the 21'st.
  • Re-Kicked with same command
  • Tagging finished fine (this time)
  • Builds finished fine, except win32.
    • Retriggered on web UI suspecting a random-red.
  • Failed again, investigation on the actual issue led me to realize that cb-sea-win32-tbox has a builds drive as FAT32 and this error is caused by that.
  • Clobbered again and retriggered on web UI.
  • Win32 Build finished fine, due to manual web-UI trigger repacks did not get triggered, did those with the following command:
cd /builds/buildbot/master01/tools/buildbot-helpers
wget -O shipped-locales http://hg.mozilla.org/releases/comm-release/raw-file/SEAMONKEY_2_5_BUILD1/suite/locales/shipped-locales
/builds/buildbot/master01/bin/python force_release_l10n.py -m http://cb-seamonkey-linuxmaster-01.mozilla.org:8010 \
  -t SEAMONKEY_2_5_RELEASE -v -b releases/mozilla-release -p win32 \
  -n Callek -c "Need to force all win32 repacks" -s shipped-locales
rm shipped-locales
  • All Repacks finished fine.

Update Version for stage scripts

On stage-old.mozilla.org, modified ~/versions.sh for the current release run.

Signing

  • Our mac builds (non en-US) uploaded to mac64/ so I had to move them over to mac/ on stage, for both updates and builds.
    • Logged onto stage-old.mozilla.org and ran sh ~/mac64tomac.sh
    • which moves all mac64 files/directories to mac, and removes the mac64 dir.
  • We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
  • Logged onto stage-old.mozilla.org and ran sh ~/fakesign.sh

Updates and Verification

  • _l10n_verify and updates started automatically, triggered by the fake-signing.
    • L10n verification is mostly useless, since we have lots of expected changed strings.
  • Update and Update verification were both good.

Copy Language Packs

Used langpackmove.sh as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release.

Zipcopy

Used zipcopy.sh as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release.

Create Checksums

With make-checksums.sh as documented in 2.0.3 notes, created MD5SUMS and SHA1SUMS files containing all files we release - copying the README from last time and replacing the versions as needed, as well as doing the same for Linux x86_64.

Push To Mirrors

Used mirrorpush.sh as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up.

Final Verification

Used 'Force Build' to start the final_verification builder; all tested URLs are HTTP 200 and 302 - ready for going public!

Push website updates Live

locally: 

cvs up -Pd && patch -p0 < patch && cvs ci -m ....

Push Updates to the beta Channel

Once website updates are live

On aus |/opt/aus2/snippets/staging/|: 

~/bin/backupsnip Sea*2.5-build1
~/bin/pushsnip Sea*2.5-build1

Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.5b3 win32 (all locales) for them to scan, and be sure there are no false-positives.

  • Used |viruspush.sh| on stage for this.

Send Announce

Send the announcement to newsgroups and about-mozilla in one e-mail, send to announce@ in another.

Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.5&oldid=379730"