Notes About Releasing

Please update the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Also check the "known issues" page.

• Xulrunner source builder timed out
• updates failed because no beta snippets were created
• update verify failed on windows 'is'

Build Engineers

catlee - bug 669944

Signed-off Revision(s)

Build 1: 07cfee2cd139

L10N changesets

No changes

Tags

Build #	Tag	Changeset
1	GECKO501_2011070717_RELBRANCH	07cfee2cd139
	FIREFOX_5_0_1_BUILD1 FIREFOX_5_0_1_RELEASE	3ded311d93ad

Build data

Build #	Type	Build ID	Build machine	Time to build
1	Linux
	Linux64
	Mac
	Windows

Notes

Build 1

• Marked "Any master", "mozilla-release", "Any builder" for a clobber
• Set reserved_slaves_bm07-build1 to 5
• Landed release config patch
• Tagged buildbot-configs, buildbotcustom, and tools with FIREFOX_5_0_1_{RELEASE,BUILD1}
• Updated checkouts on bm07, reconfiged
• Ran release_sanity.py:

cd /builds/buildbot/build1/master
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 5.0.1 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py --dryrun localhost:9001

• • Failed beacuse of missing l10n-changesets_mozilla-release symlink.
    • Added it, ran release sanity again.
  • Failed with:

2011-07-07 17:55:38,501 : ERROR : cannot find l10n dashboard at https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx5.0.1
2011-07-07 17:55:38,501 : ERROR : Error verifying l10n dashboard changesets

• • • This is ignorable, because the dashboard was never updated for 5.0.1.
• Kicked off automation with:

source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 5.0.1 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py --bypass-check localhost:9001

Tag

No problems

Start autosign

Once mozilla-release was tagged, on keymaster, started signcodepwd.exe, opened a cygwin terminal and ran the following:

PRODUCT=firefox
VERSION=5.0.1
BUILD=1
TAG=FIREFOX_5_0_1_RELEASE
REPO='releases/mozilla-release'
EMAIL=release@mozilla.com
KEYDIR=d:/2010-keys
RELCONFIG=mozilla/release-firefox-mozilla-release.py

cd ${HOME}/hg-tools/
hg pull && hg up -r ${TAG}

mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
rsync -av ~/hg-tools/lib/python/ ./lib/python/
make autosign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG}

Updates

Failed to upload beta snippets because they weren't created. Probably due to http://mxr.mozilla.org/mozilla/source/tools/patcher-configs/mozRelease-branch-patcher2.cfg#5

# on mv-moz2-linux-ix-slave17
cd /builds/slave/rel-m-rel-updates/build/temp/firefox/5.0-5.0.1
rsync -a aus2.test/ aus2.beta/
find aus2.beta -name releasetest -exec rm -rf {} \;
for d in `find aus2.beta -type d -name betatest`; do mv $d ${d/betatest/beta}; done
rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' aus2.beta/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-5.0.1-build1-beta

Compared snippets:

bash /builds/slave/rel-m-rel-updates/tools/release/compare-channel-snippets.sh aus2 release aus2.test releasetest
bash /builds/slave/rel-m-rel-updates/tools/release/compare-channel-snippets.sh aus2.beta beta aus2.test betatest

Kicked update verify:

# On my local machine, to kick off update verify
for p in linux linux64 macosx64 win32; do
  for i in 1 2 3 4 5 6 7 8 9 10; do
    curl "http://buildbot-master07.build.mozilla.org:8001/builders/release-mozilla-release-${p}_update_verify_${i}%2F10/force" >/dev/null
  done
done

Update verify failed on windows 5/10:

FAIL: no partial update found for https://aus3.mozilla.org/update/1/Firefox/5.0/20110615151330/WINNT_x86-msvc/is/betatest/update.xml?force=1
FAIL: download_mars returned non-zero exit code: 1
Using  https://aus3.mozilla.org/update/1/Firefox/5.0/20110615151330/WINNT_x86-msvc/is/betatest/update.xml?force=1

AUS response looks fine, as does referenced partial mar. re-triggered check. The rebuild passed.

Prep mac only snippets

# cltbld@aus2-staging
rsync -a Firefox-5.0.1-build1/ Firefox-5.0.1-build1-maconly/

find Firefox-5.0.1-build1-maconly/ -maxdepth 3 -type d -name 'Linux*' -exec rm -rf {} \;
find Firefox-5.0.1-build1-maconly/ -maxdepth 3 -type d -name 'WINNT*' -exec rm -rf {} \;

Permissions check & Virus Scan

Had to be triggered manually because updates failed.

Both completed successfully.

Push to Mirrors

Used "force build" to start the release-mozilla-release-push_to_mirrors builder with the following properties:

• release_config: mozilla/release-firefox-mozilla-release.py
• script_repo_revision: FIREFOX_5_0_1_RELEASE

Manually updated stage:/pub/mozilla.org/mozilla.org/zz/rsyncd-mozilla-current.exclude:

• Removed 5.0
• Added 5.0.1

Also pointing Thunderbird to 5.0 instead of ancient 3.1.7.

Final Verification

Mac failed with:

FAIL: no partial update found for https://aus3.mozilla.org/update/1/Firefox/5.0/20110615151330/Darwin_x86_64-gcc3-u-i386-x86_64/kn/releasetest/update.xml?force=1
FAIL: download_mars returned non-zero exit code: 1

Loading the URL manually shows partial and complete updates offered, bouncer works for the partial, and the partial is present on dm-download02. Putting it down to a transient error.

Other platforms are a bogus kind of green - releasetest has 5.0.1 on it when it shouldn't.

Push release channel snippets

# cltbld@aus2-staging
cd /opt/aus2/snippets/staging
~/bin/backupsnip Firefox-5.0.1-build1-maconly
~/bin/pushsnip   Firefox-5.0.1-build1-maconly