Releases/Thunderbird 17.0.3/BuildNotes

< Releases
Revision as of 17:41, 19 February 2013 by Bhearsum (talk | contribs)

Build 1

Checklist

Notes

  • Submitted to ship it.
  • Coop reviewed and marked as ready.

Update the correct config

Because of bug 815302 we updated the wrong release config. To fix:

# cltbld@buildbot-master36
cd /builds/buildbot/build_scheduler/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 17.0.3 --branch comm-esr17 --build-number 1 --release-config release-thunderbird-comm-release.py --skip-reconfig --bypass-l10n-dashboard-check --bypass-check localhost:9301
  • reconfiged the build + scheduler masters by hand
  • reran release sanity to start the release:
# cltbld@buildbot-master36
cd /builds/buildbot/build_scheduler/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 17.0.3 --branch comm-esr17 --build-number 1 --release-config release-thunderbird-comm-release.py --skip-reconfig --bypass-l10n-dashboard-check localhost:9301

Disable pymake

win32 build failed because it tried to use pymake, which isn't supported on Gecko 17 bug 841898. FIXME - why didn't this get caught in pre-release builds? Does Thunderbird-Release not build the same thing that we're going to release with?

Landed the patches from that bug, retagged buildbot-configs and buildbotcustom, reconfiged build masters, and then used "rebuild" to restart the win32 build.

Retrigger mac builds

Mac build failed with a weird error:

Traceback (most recent call last):
  File "/builds/slave/tb-rel-c-rel-osx64_bld-0000000/tools/release/signing/signtool.py", line 194, in <module>
    main()
  File "/builds/slave/tb-rel-c-rel-osx64_bld-0000000/tools/release/signing/signtool.py", line 156, in main
    token = open(options.tokenfile, 'rb').read()
IOError: [Errno 2] No such file or directory: '/builds/slave/tb-rel-c-rel-osx64_bld-0000000/token'

Almost seems related to the shortening of the build directory done while disabling pymake, but there's no evidence that the build directory changed mid-build in http://buildbot-master34.srv.releng.scl3.mozilla.com:8001/builders/release-comm-release-macosx64_build/builds/9. Someone retriggered it (don't know who), and it succeeded.

Repacks subsequently failed because the en-US was retriggered with "force build" instead of "rebuild", which meant that "script_repo_revision" wasn't set. (FIXME: we should make sure it's always set). Used "force build" to start those builders with "script_repo_revision" set to THUNDERBIRD_17_0_3_RELEASE

Push snippets

As tbirdbld@aus3-staging

cd /opt/aus2/snippets/staging
~/bin/pushsnip Thunderbird-17.0.3-build1

Postrelease

Used "force build" to start postrelease builder.