|
|
| (8 intermediate revisions by the same user not shown) |
| Line 40: |
Line 40: |
| | rowspan="4" | 1 | | | rowspan="4" | 1 |
| | Linux | | | Linux |
| | rowspan="4" | | | | rowspan="4" | 20120531155942 |
| | | | | linux-ix-slave14 |
| | | | | 1 hrs, 7 mins, 8 secs |
| |- | | |- |
| | Linux64 | | | Linux64 |
| | | | | linux64-ix-slave21 |
| | | | | 1 hrs, 5 mins, 50 secs |
| |- | | |- |
| | Mac | | | Mac |
| | | | | moz2-darwin10-slave42 |
| | | | | 3 hrs, 21 mins, 10 secs |
| |- | | |- |
| | Windows | | | Windows |
| | | | | mw32-ix-slave13 |
| | | | | 3 hrs, 30 mins, 34 secs |
| |} | | |} |
|
| |
|
| Line 60: |
Line 60: |
| =Notes= | | =Notes= |
| ==Build 1== | | ==Build 1== |
| ===Diff mozconfigs===
| |
|
| |
| ===Preparing to start Automation=== | | ===Preparing to start Automation=== |
| * Set clobbers for release-mozilla-beta on all masters | | * Set clobbers for release-mozilla-beta on all masters |
| Line 98: |
Line 96: |
| * start automation | | * start automation |
| ** the same command as above but without the "--dryrun" | | ** the same command as above but without the "--dryrun" |
|
| |
| '''DONE TO HERE'''
| |
|
| |
| * reconfigure other masters (or ask the buildduty person to do this) <em>if you have done a merge (and not double-land) to production</em>
| |
|
| |
|
| === E-mail Metrics === | | === E-mail Metrics === |
| Line 108: |
Line 102: |
| Firefox,firefox,firefox,13.0b7,13.0 | | Firefox,firefox,firefox,13.0b7,13.0 |
|
| |
|
| === Tag === | | === Tag -> Ready for release === |
| | | All automated; no problems \o/ |
| === Bouncer Submitter ===
| |
| | |
| | |
| === Source ===
| |
| | |
| | |
| === Build ===
| |
| ==== Firefox ====
| |
| | |
| ===== Firefox repacks =====
| |
| | |
| ==== Fennec ====
| |
|
| |
|
| ===== Fennec repacks =====
| | Reset reserved_slaves to 0 |
| | |
| === Unittests / Talos ===
| |
| <small>[[Release:Release_Automation_on_Mercurial:Documentation#Talos_.26_Unittests|details]]</small>
| |
| # Look to see that they ran
| |
| # Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
| |
| # Make sure there's no red/failures that we need to have a dev look at
| |
| | |
| === XULRunner ===
| |
| | |
| ====Source====
| |
| | |
| ====Build====
| |
| | |
| === Partner Repack ===
| |
| ==== Firefox ====
| |
| ==== Fennec ====
| |
| | |
| === Android Signing ===
| |
| Instructions in [https://intranet.mozilla.org/Build:MobileSigning MobileSigning]
| |
| | |
| Now run on signing1.
| |
| === L10N verify ===
| |
| | |
| | |
| === Checksums ===
| |
| | |
| === Updates ===
| |
| | |
| ==== Update verify ====
| |
| | |
| === Major Update ===
| |
| 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.
| |
| | |
| ==== Major Update verify ====
| |
| | |
| === Reset reserved slaves ===
| |
| | |
| === Check permissions / AV scan ===
| |
| It is supposed to be triggered automatically after updates are done.
| |
| File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Documentation#Antivirus_check|details]]</small>
| |
| | |
| === Push to internal mirrors ===
| |
| This is done by automation for rapid release betas. '''Note''': if you have to reconfig the release buildbot master in during the release, the uptake monitoring will fail ({{bug|629648}}). That means you'll need to manually send the "ready for releasetest" emails when you believe things are "good enough". Refer to a prior release for email details.
| |
| | |
| For other releases, this should be done manually at this point, after check permissions / AV scan have completed.
| |
| * Make sure the rsync excludes have been updated ([[Releases/BuildNotesTemplate#Edit_rsync_exclude_files]])
| |
| * 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)
| |
|
| |
|
| === Going to Beta === | | === Going to Beta === |
| <font color='orange'>NOTE: Skip to "Before Release Day" for '''beta''' releases</font>
| |
|
| |
|
| ==== Run backupsnip ==== | | ==== 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>
| | <pre> |
| | | backupsnip Firefox-13.0b7-build1 |
| Remember to ssh to aus3-staging using your short LDAP name and then run <code>sudo su - ffxbld</code> once on. If you intend to use screen, initiate your screen session while you are still yourself.
| | </pre> |
|
| |
|
| ==== Push to beta ==== | | ==== Push to beta ==== |
| Wait for "go" from release managers<br /> | | Wait for "go" from release managers<br /> |
| For Firefox: | | For Firefox: |
| * Publish (and record run time here): <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Beta_Release_.28Firefox_only.29|details]]''</small> | | * Publish (and record run time here): |
| * on completion, email r-d that VERSION updates are live on the beta channel
| | <pre> |
| | pushsnip Firefox-13.0b7-build1 |
|
| |
|
| For Android:
| | cat Firefox-13.0b7-build1.time |
| * publish on Google Play (nee Android Marketplace), using [[#Publish_Fennec_to_the_Android_Market|instructions below]]
| | real 285.03 |
| * on completions, email r-d that VERSION is live on Google Play
| | user 1.70 |
| | sys 5.44 |
| | </pre> |
|
| |
|
| Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket. | | 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 === |
| ==== Publish Fennec to the Play Store (for beta releases and release releases) ====
| |
| =====Push the files (for beta releases and release releases)=====
| |
| * Use [http://hg.mozilla.org/build/braindump/file/tip/releases-related/push_fennec.sh this script] and run it as ffxbld@stage (please push you changes prior to using it, and grab latest on stage via <tt>curl -O http://hg.mozilla.org/build/braindump/raw-file/tip/releases-related/push_fennec.sh</tt>)
| |
|
| |
| =====Play Store (for beta releases and release releases)=====
| |
| '''IMPORTANT -''' Make sure to follow instructions!
| |
| * download multi apk (e.g. [http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/10.0b6-candidates/build1/android/multi/fennec-10.0b6.multi.android-arm.apk 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 ==== | | ====Push XULRunner to Mirrors ==== |
|
| |
|
| Line 268: |
Line 160: |
| ==== Push to Release Channel (for beta releases and release releases) ==== | | ==== Push to Release Channel (for beta releases and release releases) ==== |
| Once there is enough uptake and we get "go" from release driver. | | 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 ====
| |
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:
Build Engineers
{catlee} - Tracking bug: bug 760219
Signed-off Revision(s)
Build 1: b8b0ed817c31
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
|
| 1
|
GECKO130_2012053115_RELBRANCH, FIREFOX_13_0b7_BUILD1 FIREFOX_13_0b7_RELEASE
|
b8b0ed817c31
|
Build data
Firefox
| Build #
|
Type
|
Build ID
|
Build machine
|
Time to build
|
| 1
|
Linux
|
20120531155942
|
linux-ix-slave14
|
1 hrs, 7 mins, 8 secs
|
| Linux64
|
linux64-ix-slave21
|
1 hrs, 5 mins, 50 secs
|
| Mac
|
moz2-darwin10-slave42
|
3 hrs, 21 mins, 10 secs
|
| Windows
|
mw32-ix-slave13
|
3 hrs, 30 mins, 34 secs
|
Notes
Build 1
Preparing to start Automation
- Set clobbers for release-mozilla-beta on all masters
- Set reserved slaves on bm13:
[cltbld@buildbot-master13 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master13 master]$ cat reserved_slaves
5
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/13.0b7-candidates
ln -s ../candidates/13.0b7-candidates 13.0b7-candidates
- Update l10n changesets for desktop, mobile : No changes.
- Landed configs: default production
- Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
hg tag -f FIREFOX_13_0b7_RELEASE FIREFOX_13_0b7_BUILD1
- update and reconfigure the master
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u catlee -V 13.0b7 --branch mozilla-beta --build-number 1 \
--release-config release-firefox-mozilla-beta.py --products firefox --dryrun localhost:9001
- start automation
- the same command as above but without the "--dryrun"
E-mail Metrics
Use the address "metrics-alerts < AT > mozilla < PERIOD > org". Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on #metrics.
Firefox,firefox,firefox,13.0b7,13.0
Tag -> Ready for release
All automated; no problems \o/
Reset reserved_slaves to 0
Going to Beta
Run backupsnip
backupsnip Firefox-13.0b7-build1
Push to beta
Wait for "go" from release managers
For Firefox:
- Publish (and record run time here):
pushsnip Firefox-13.0b7-build1
cat Firefox-13.0b7-build1.time
real 285.03
user 1.70
sys 5.44
Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
Release Day
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:
- Automatic (idle time check) update links:
- Manual update links:
Push to Release Channel (for beta releases and release releases)
Once there is enough uptake and we get "go" from release driver.