Build 1

Checklist

• Submit to Ship It ^{DESKTOP MOBILE RELEASE BETA ESR}
• Apply Throttling ^{DESKTOP RELEASE}
• Verify throttling ^{DESKTOP RELEASE}
• Run pushsnip ^{DESKTOP RELEASE BETA ESR}
• Post-release tasks ^{DESKTOP RELEASE BETA ESR}

Notes

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

Disable l10n dashboard check

This was wrongly enabled and not caught at review time. It was flipped off and resubmitted.

Fix failed updates

There was an existing block for 17.0.3esr in the config that needed to removed: https://hg.mozilla.org/build/tools/rev/b61bcb936ce6

The automation also wanted to create the past-update entry for 17.0.1esr->17.0.2esr, but it already existed. It was removed: https://hg.mozilla.org/build/tools/rev/701e6030b908

Retriggered the builder via 'Force Build.'

Snippets weren't generated for 10.0.12, so I created them by hand on the machine that ran the updates builder (mv-moz2-linux-ix-slave18):

$ BUILDID11=20121115102332
$ BUILDID12=20130103094221
$ cd /builds/slave/rel-m-esr17-updates/
$ for d in aus2.test aus2; do
     cd ${d}/Firefox
     cp -r 10.0.11 10.0.12
     cd 10.0.12
     for plat in Darwin_x86_64-gcc3-u-i386-x86_64 Darwin_x86-gcc3-u-i386-x86_64 Linux_x86_64-gcc3 Linux_x86-gcc3 WINNT_x86-msvc; do
       mv ${plat}/${BUILDID11} $plat/${BUILDID12};
     done
     cd ../../..
$ cd /builds/slave/rel-m-esr17-updates/
$ rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2.test/ \
    ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-17.0.3esr-build1-test
$ ssh -t -l ffxbld '-oIdentityFile=~/.ssh/auspush' aus3-staging.mozilla.org \
    '~/bin/pushsnip Firefox-17.0.3esr-build1-test'
$ rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2/ \
    ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-17.0.3esr-build1

pushnip

$ ssh -t -l ffxbld '-oIdentityFile=~/.ssh/auspush' aus3-staging.mozilla.org \
    '~/bin/pushsnip Firefox-17.0.3esr-build1'

Throttling

Callek in bug 841908 accidentally made 17.0 and 17.0.1 esr's apply to Firefox19 throttling, that is at 50% rather than unthrottled, that was resolved in an additional patch in bug 802167 with an extra production push.

Unthrottled on 2013/02/25 with a follow-up patch to bug 802167.