Releases/Firefox 13.0b1/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:
= Bugs hit =
= Bugs hit =
Enter any bugs pre-existing or newly discovered and filed during the release:
Enter any bugs pre-existing or newly discovered and filed during the release:
* {{bug|}} - description
*
* {{bug|747481}} pushsnip for test snippets didn't work properly because of file ownership on aus2-staging.  test snippets were pushed but the non-test snippets weren't transfered.  The following command was used to transfer the non-test snippets:
* {{bug|747481}} pushsnip for test snippets didn't work properly because of file ownership on aus2-staging.  test snippets were pushed but the non-test snippets weren't transfered.  The following command was used to transfer the non-test snippets:
  cd /builds/slave/rel-m-beta-updates/build/temp/firefox/12.0b6-13.0b1
  cd /builds/slave/rel-m-beta-updates/build/temp/firefox/12.0b6-13.0b1
  rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-13.0b1-build1
  rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-13.0b1-build1


Update verify needed to be triggered manually
Update and final verify needed to be triggered manually


=Build Engineers=
=Build Engineers=
Line 171: Line 168:
Now run on signing1.
Now run on signing1.
=== L10N verify ===
=== L10N verify ===
 
no problems


=== Checksums ===
=== Checksums ===
 
no problems
=== Updates ===
=== Updates ===
Failed gracefully during pushsnip.  test updates were pushed but non-test snippets weren't uploaded.  See issues hit above to see how this was worked around
Failed gracefully during pushsnip.  test updates were pushed but non-test snippets weren't uploaded.  See issues hit above to see how this was worked around
==== Update verify ====
==== Update verify ====
triggered manually, no problems


=== Major Update ===
=== Reset reserved slaves ===
Major update generation is not kicked off automatically. You should only create them once the final builds for the "latest" build are ready.
For instance, the 3.6.26 builds got created a week before the 10.0 release but the "final" 10.0 builds were not created after few days.


Follow instructions from the [[Release:Release_Automation_on_Mercurial:Documentation#Major_Update_.28Firefox_only.29|Major update]] documentation.
[cltbld@buildbot-master08 master]$ echo 0 > reserved_slaves_bm08-build1
 
==== Major Update verify ====
 
=== Reset reserved slaves ===


=== Check permissions / AV scan ===
=== Check permissions / AV scan ===
Line 196: Line 188:
This is done by automation for rapid release betas.
This is done by automation for rapid release betas.


For other releases, this should be done manually at this point, after check permissions / AV scan have completed.
=== Final verification ===
* Make sure the rsync excludes have been updated ([[Releases/BuildNotesTemplate#Edit_rsync_exclude_files]])
Needed to be triggered manually
* Force build the push to mirrors builder. Make sure at least 15 minutes have elapsed since editing the rysnc module to give it time to sync out.


[https://intranet.mozilla.org/ReleaseEngineering/Release/Primer#Mirrors_.28internal_.26_external.29 Mirrors Policy]
=== Final verification ===
Record receipt of "completed_final_verification" emails (1 per platform)
Record receipt of "completed_final_verification" emails (1 per platform)
=== Going to Beta ===
<font color='orange'>NOTE: Skip to "Before Release Day" for '''beta''' releases</font>
==== Run backupsnip ====
NOTE: Remember to do this at least '''2 hours''' ahead of the expected "go to beta" email. <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Prepare_for_Beta_Release_.28Firefox_only.29|details]]''</small>
==== Push to beta ====
Wait for "go" from release managers<br />
For Firefox:
* Publish (and record run time here): <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Beta_Release_.28Firefox_only.29|details]]''</small>
* on completion, email r-d that VERSION updates are live on the beta channel
For Android:
* publish on Google Play (nee Android Marketplace), using [[#Publish_Fennec_to_the_Android_Market|instructions below]]
* on completions, email r-d that VERSION is live on Google Play
Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
=== Before Release Day ===
<!-- not for beta -->
Assuming this is not a chemspill.
==== Run backupsnip for release snippets ====
Do this the night before release day as it can take up to two hours.
=== Push index file to mirrors ===
=== Push to external mirrors ===
If this is a chemspill you will want to ping justdave (or other sysadmin) in #release-drivers and ask them to enable CDN.
* Remove previously added blacklisting entry from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
* Replace old version with the current one in stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude
See [https://intranet.mozilla.org/RelEngWiki/index.php/Managing_Rsync_Modules details]


=== Release Day ===
=== Release Day ===

Revision as of 16:43, 26 April 2012

Notes About Releasing

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

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

  • bug 747481 pushsnip for test snippets didn't work properly because of file ownership on aus2-staging. test snippets were pushed but the non-test snippets weren't transfered. The following command was used to transfer the non-test snippets:
cd /builds/slave/rel-m-beta-updates/build/temp/firefox/12.0b6-13.0b1
rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-13.0b1-build1

Update and final verify needed to be triggered manually

Build Engineers

{jhford} - Tracking bug: bug 744590

Signed-off Revision(s)

Build 1: e60ca2e387a8

L10N changesets

Instructions on how to get them

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build # Branch, Tags Changeset
MOBILE130_2012042512_RELBRANCH FENNEC_13_0b1_BUILD1 FENNEC_13_0b1_RELEASE e8c31168413b
GECKO130_2012042512_RELBRANCH FIREFOX_13_0b1_BUILD1 FIREFOX_13_0b1_RELEASE f16e48c88ac3

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120425123149 mv-moz2-linux-ix-slave04 1 hrs, 4 mins, 8 secs
Linux64 linux64-ix-slave07 1 hrs, 2 mins, 19 secs
Mac moz2-darwin10-slave43 3 hrs, 19 mins, 29 secs
Windows mw32-ix-slave10 3 hrs, 27 mins, 39 secs

Fennec

Build # Type Build ID Build machine Time to build
1 android-xul 20120425123100 mv-moz2-linux-ix-slave19 47 mins, 50 secs

Notes

Build 1

Diff mozconfigs

If this is a *.0 beta -> release. May also need to update the whitelist of nightly vs release differences for release sanity.

Preparing to start Automation

detailed instructions

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
    • set any master, mozilla-beta, any builder on apr-24 at 5:52pm
  • Reserve slaves, e.g.:
[cltbld@buildbot-master08 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master08 master]$ cat reserved_slaves_bm08-build1 
8
  • 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)
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
  • Update l10n changesets for desktop, mobile
  • Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
    • Sample command for Firefox 10.0 beta 5 build 1:
bash shortcut: hg tag -f {FIREFOX,FENNEC}_13_0b1_{RELEASE,BUILD1}
  • update and reconfigure the master
  • start automation ← monitor progress on buildbot (e.g. beta)
# Combined release
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --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

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org" 

Firefox,firefox,firefox,13.0b1,13.0
Fennec,firefox-mobile,fennec,13.0b1,13.0

Tag

no problems

Bouncer Submitter

no problems

Source

no problems

Build

Firefox

no problems

Firefox repacks

linux, linux64 finished and good

Fennec

Fennec repacks

Unittests / Talos

details

  1. Look to see that they ran
  2. Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
  3. Make sure there's no red/failures that we need to have a dev look at

XULRunner

Source

no problems

Build

no problems

Android Signing

Instructions in MobileSigning

Now run on signing1.

L10N verify

no problems

Checksums

no problems

Updates

Failed gracefully during pushsnip. test updates were pushed but non-test snippets weren't uploaded. See issues hit above to see how this was worked around

Update verify

triggered manually, no problems

Reset reserved slaves

[cltbld@buildbot-master08 master]$ echo 0 > reserved_slaves_bm08-build1

Check permissions / AV scan

It is supposed to be triggered automatically after updates are done. File a bug if it doesn't. details

Push to internal mirrors

This is done by automation for rapid release betas.

Final verification

Needed to be triggered manually

Record receipt of "completed_final_verification" emails (1 per platform)

Release Day

Publish Fennec to the Play Store (for beta releases and release releases)

Push the files (for beta releases and release releases)
Play Store (for beta releases and release releases)

IMPORTANT - Make sure to follow instructions!

  • download multi apk (e.g. multi/fennec-10.0b6.multi.android-arm.apk)
  • visit https://market.android.com/publish
  • choose "Firefox Beta" or "Firefox"
  • select the "APK Files" tab and choose "Upload APK"
    • choose the multi apk that you downloaded and hit "upload"
      • NOTE: the progress bar does not seem to show progress (at least on Google Chrome)
    • when it finishes uploading, verify VersionCode is the build date (almost anyway, the market reports an hour later than our buildID)
    • hit "Save"
  • activate new apk (You should see an Error message since both apk's are active)
  • deactivate old apk (You should not see the Error message anymore)
  • hit "Save"
  • If this is a beta 1, go to "Product Details" tab -> Recent Changes, change the url to http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/
    • and hit "Save"

Push XULRunner to Mirrors

Update XULRunner wiki page

For major releases or chemspills, update the links on:

Also for older releases:

Check Throttling

See http://update-watch.localgho.st/release/ for example AUS links

Some links to check:

Push to Release Channel (for beta releases and release releases)

Once there is enough uptake and we get "go" from release driver.

Update symlinks

Once we're signed off on the release channel.

Remove index.html files

If you created them earlier to hide the release.

Update browser choice website

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_13.0b1/BuildNotes&oldid=424666"