Releases/Firefox 14.0b11/BuildNotes: Difference between revisions

m
 
(16 intermediate revisions by the same user not shown)
Line 6: Line 6:
* <strike>[[Release:Release_Automation_on_Mercurial:Build#E-mail_Metrics | E-mail Metrics]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Build#E-mail_Metrics | E-mail Metrics]]</strike>
* <strike>[https://intranet.mozilla.org/RelEngWiki/index.php/Signing#Android_Signing Sign Android builds]</strike>
* <strike>[https://intranet.mozilla.org/RelEngWiki/index.php/Signing#Android_Signing Sign Android builds]</strike>
* [[Release:Release_Automation_on_Mercurial:Build#Reset_reserved_slaves | Reset reserved_slaves]]
* <strike> [[Release:Release_Automation_on_Mercurial:Build#Reset_reserved_slaves | Reset reserved_slaves]] </strike>
* [[Release:Release_Automation_on_Mercurial:Updates#Publish_Fennec | Publish Fennec]]
* <strike>[[Release:Release_Automation_on_Mercurial:Updates#Publish_Fennec | Publish Fennec]] </strike>
* [[Release:Release_Automation_on_Mercurial:Updates#Push_snippets | Run pushsnip]]
* <strike> [[Release:Release_Automation_on_Mercurial:Updates#Push_snippets | Run pushsnip]] </strike>


= Notes =
= Notes =
== Build 1 ==
== Build 1 ==
=== Starting the Release ===
=== Starting the Release ===
Tracking bug is [http://bugs.mozilla.org/760629 Bug 760629]
* L10N Changesets *
* L10N Changesets *
Currently we have separate changesets files for Fennec and Firefox. Both are generated from the [https://l10n.mozilla.org/shipping/milestones l10n dashboard]<br />
Currently we have separate changesets files for Fennec and Firefox. Both are generated from the [https://l10n.mozilla.org/shipping/milestones l10n dashboard]<br />
Line 35: Line 38:
I didn't have rights to create the milestones so Armen created them and emailed Axel to grant my permissions for next time.
I didn't have rights to create the milestones so Armen created them and emailed Axel to grant my permissions for next time.


==Fennec==
====Fennec====
* Click "ship it" to load up the milestone (eg: Fennec 14 Beta Build 11)
* Click "ship it" to load up the milestone (eg: Fennec 14 Beta Build 11)
* This will take you to a page like [https://l10n.mozilla.org/shipping/confirm-ship?ms=fennec14_beta_b11 https://l10n.mozilla.org/shipping/confirm-ship?ms=fennec14_beta_b11]
* This will take you to a page like [https://l10n.mozilla.org/shipping/confirm-ship?ms=fennec14_beta_b11 https://l10n.mozilla.org/shipping/confirm-ship?ms=fennec14_beta_b11]
Line 51: Line 54:
* select "Ship it" to preserve the record of what was shipped
* select "Ship it" to preserve the record of what was shipped


==Firefox==
====Firefox====


* Click "ship it" to load up the milestone (eg: Firefox 14 Beta Build 11)
* Click "ship it" to load up the milestone (eg: Firefox 14 Beta Build 11)
Line 60: Line 63:
* select "Ship it"
* select "Ship it"
** <small>if you forget the URL, you can recreate the URL by judicious modification of the URL from the prior build notes</small>
** <small>if you forget the URL, you can recreate the URL by judicious modification of the URL from the prior build notes</small>


* Set reserved_slaves:
* Set reserved_slaves:
Line 98: Line 100:
  PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u kmoir -V 14.0b11 --branch mozilla-beta --build-number 1    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  localhost:9001
  PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u kmoir -V 14.0b11 --branch mozilla-beta --build-number 1    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  localhost:9001


The release emails indicated that the Fennec build being created was 14.0b2 which was completely unexpected.  After talking with rail, callek, bhearsum and catlee, they determined that the problem was that bm12 took the Fennec build instead of bm13 and it was pointing to mozilla-beta since the 14.0 release was run from mozilla-beta.  The sendchange to so the trigger 14.0b11 builds also triggered 14.0 build2 again.  The fennec release configs point to mozilla-beta, so they advised me to change release-fennec-mozilla-release.py to point to mozilla-release, land in production, retag the buildbot-configs, reconfig bm12 and bm13 and trigger the Fennec build again.
The release emails indicated that the Fennec build being created was 14.0b2 which was completely unexpected.  After talking with rail, callek, bhearsum and catlee, they determined that the problem was that bm12 took the Fennec build instead of bm13 and it was pointing to mozilla-beta since the 14.0 release was run from mozilla-beta.  The sendchange to trigger 14.0b11 builds triggered 14.0 build2 again.  The fennec release configs point to mozilla-beta, so they advised me to change release-fennec-mozilla-release.py to point to mozilla-release, land in production, retag the buildbot-configs, reconfig bm12 and bm13 and trigger the Fennec build again.


I started the Fennec build with the following command after running a successful release sanity.
I started the Fennec build with the following command after running a successful release sanity.
Line 107: Line 109:
     --release-config release-fennec-mozilla-beta.py --products fennec  \
     --release-config release-fennec-mozilla-beta.py --products fennec  \
     localhost:9001
     localhost:9001
The Firefox build stopped because of problems running the antivirus scans, I had to restart the [http://buildbot-master13.build.scl1.mozilla.com:8001/builders/release-mozilla-beta-push_to_mirrors push to mirrors script].


=== E-mailed Metrics ===
=== E-mailed Metrics ===
Line 129: Line 133:
  cd /opt/aus2/snippets/staging
  cd /opt/aus2/snippets/staging
  ~/bin/pushsnip Firefox-14.0b11-build1
  ~/bin/pushsnip Firefox-14.0b11-build1
=== Starting the Automation ===
* Updated and [https://wiki.mozilla.org/ReleaseEngineering/Landing_Buildbot_Master_Changes reconfiged] buildbot-master13
* Ran release sanity:
<pre>
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u kmoir -V 14.0b11 --branch mozilla-beta --build-number 1 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    --dryrun localhost:9001
</pre>
* No issues discovered by release sanity, so I started the release:
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u kmoir -V 14.0b11 --branch mozilla-beta --build-number 1 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    localhost:9001
The release emails indicated that the Fennec build being created was 14.0b2 which was completely unexpected.  After talking with rail, callek, bhearsum and catlee, they determined that the problem was that bm12 took the Fennec build instead of bm13 and it was pointing to mozilla-beta since the 14.0 release was run mozilla-beta.  The sendchange to so the trigger 14.0b11 builds also triggered 14.0 build2 again.  The fennec release configs point to mozilla-beta, so they advised me to change release-fennec-mozilla-release.py to point to mozilla-release, land in production, retag the buildbot-configs, reconfig bm12 and bm13 and trigger the Fennec build again.
Fennec process produced the wrong build.  This was fixed by the patch in bug https://bug760629.bugzilla.mozilla.org/attachment.cgi?id=639171
Retagged buildbot-configs, Reconfiged bm12 and 13 and ran a Fennec only build.
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u kmoir -V 14.0b11 --branch mozilla-beta --build-number 1 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    localhost:9001
=== Sign Android Builds ===
As cltsign@signing1:
<pre>
cd ~/signing-work/mozharness
hg pull -u && hg up -C
python2.6 ~/signing-work/mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py --platform android
</pre>


=== Publish Fennec ===
=== Publish Fennec ===
* Updated push_fennec.sh as ffxbld@stage and ran it.
* Updated push_fennec.sh as ffxbld@stage and ran it.
* Uploaded APK to Google Play store and activated it.
* Uploaded APK to Google Play store and activated it.
<p><font color="red">DONE TO HERE</font></p>


= Bugs Hit =
= Bugs Hit =
* Fennec build was uploaded to 14.0-candidates (to be explained why)
* Fennec build was uploaded to 14.0-candidates
** Recover 14.0-candidates files (by chance we uploaded them to nightly/test14):
** Recover 14.0-candidates files (by chance we uploaded them to nightly/test14):
  # ffxbld@stage
  # ffxbld@stage
Line 175: Line 147:
  rsync -avP 14.0-candidates/ 14.0-candidates-borked-by-14.0b11/
  rsync -avP 14.0-candidates/ 14.0-candidates-borked-by-14.0b11/
  rsync -avP --delete /pub/mozilla.org/mobile/nightly/test14/ /pub/mozilla.org/mobile/candidates/14.0-candidates/
  rsync -avP --delete /pub/mozilla.org/mobile/nightly/test14/ /pub/mozilla.org/mobile/candidates/14.0-candidates/
* [https://bugzilla.mozilla.org/show_bug.cgi?id=771034 bug 771034] Downgrade clamav* installs on upload1/upload2.dmz.scl3 to 0.97.4 to avoid bug in 0.97.5.  This caused antivirus to fail and I had to restart the push to mirrors script.
* Kmoir's account wasn't yet updated with the correct permissions so Rail uploaded the build to Google Play.
Confirmed users
1,989

edits