Releases/Thunderbird 14.0b3/BuildNotes

Build 1

Preparing to start Automation

• Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
  • clobberer
• Reserve slaves

[cltbld@buildbot-master34 master]$ echo "6" > /builds/buildbot/build1/master/reserved_slaves

• For build1 only, create a symlink for your $version (eg 11.0b4, 10.0.2esr, 10.0.2, 3.6.27) (until bug 725839 is resolved)

# tbirdbld@stage
cd /pub/mozilla.org/thunderbird/nightly/
mkdir ../candidates/14.0b3-candidates
ln -s ../candidates/14.0b3-candidates 14.0b3-candidates

• Update l10n changesets & hit "ship it"

wget -O mozilla/l10n-changesets_thunderbird-beta  https://l10n.mozilla.org/shipping/l10n-changesets?ms=tb14_beta_b3

DONE TO HERE

• Land automation configs
• Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
  • hg tag THUNDERBIRD_14_0b3_{RELEASE,BUILD1}
• update and reconfigure the master

# this removed all local changes
cd /builds/buildbot/build1
# ('''in bugs hit''') update buildbot-configs manually - bm34 has local changes
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \
   --branch comm-beta --build-number 1 \
   --release-config release-thunderbird-comm-beta.py --products thunderbird  \
   --dryrun -l localhost:9001

• (in bugs hit): I had to run with "-m" to by-pass mozconfigs:

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u coop -V 14.0b3 \
   --branch comm-beta --build-number 1 \
   --release-config release-thunderbird-comm-beta.py --products thunderbird  \
   --dryrun -m -l localhost:9001

• start automation

cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 14.0b2 \
   --branch comm-beta --build-number 1 \
   --release-config release-thunderbird-comm-beta.py --products thunderbird  \
   -l localhost:9001

• (in bugs hit): I had to run with "-m" to by-pass mozconfigs:

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 14.0b2 \
   --branch comm-beta --build-number 1 \
   --release-config release-thunderbird-comm-beta.py --products thunderbird  \
   -m -l localhost:9001

• (in bugs hit): The master was listening to port 8001 so I stopped/started the master.
  • It burned some tagging jobs that were not running when I looked
  • I clobbered and re-triggered
  • this might have happened because I tried using "buildbot-wrangler" first (Ctrl + C) it due to lack of output and then I used release_sanity.py to start the build
• start automation ← monitor progress on buildbot (e.g. release-comm-beta)

Check that the builds are taken after tagging

• done

Branches glog

• Check that tagging created the branches and document them

http://hg.mozilla.org/releases/mozilla-beta/graph/96047 http://hg.mozilla.org/releases/comm-beta/graph/11884

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org". Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on #metrics.

Thunderbird,thunderbird,thunderbird,14.0b3,14.0

Going to Beta

Run backupsnip

# tbirdbld@aus3-staging
~/bin/backupsnip Thunderbird-14.0b3-build1

Push to beta

# tbirdbld@aus3-staging
~/bin/pushsnip Thunderbird-14.0b3-build1