SeaMonkey:Release Process:2.4b1

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.4b1

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 684648

Build Engineer

Justin Wood

Signed-off Revisions

releases/comm-beta
 e2ce5e42bbb8
releases/mozilla-beta
 ff20a21364bb
(GECKO70_2011083111_RELBRANCH)
dom-inspector
 DOMI_2_0_10_RELEASE
(DOMI_2_0_10)
chatzilla
 144f0c279a3b
venkman
 ec1bad774125

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

Build

  • Made sure all build machines have clean release directories.
    • Manually on windows, jumphost sh relclean.sh
  • Updated build/buildbot-configs 96bca8b7e9d5 for l10n and configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-beta -c "SeaMonkey 2.2b2build1" doit
  • Tagging and all builds succeeded normally

Fake tr locale

Not Needed for this build

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 new locales, and lots of expected changed strings.
  • update failed, due to the build machine putting snippets in aus2.beta/ rather than aus2/ Unsure where in the chain this bug is hiding, but fixed manually with the following command (after logging into the machine/build):
rsync -av -e "ssh -oIdentityFile=~/.ssh/seabld_dsa" aus2.beta/ seabld@aus2-community.mozilla.org:/opt/aus2/snippets/staging/SeaMonkey-2.4b1-build1
  • the Update verification failed on all platforms.
    • This was due to a config issue which marked our old version (for these verify scripts) as 3.3.3 and of course no updates found. Fixed configs and re-ran.

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;

Push Updates to the beta Channel

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

~/bin/backupsnip Sea*2.4b1*build1
~/bin/pushsnip Sea*2.4b1*build1

Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.1rc1 en-us win32 for them to scan, and be sure there are no false-positives.

Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.4b1&oldid=348275"