Releases/SampleBuildNotes: Difference between revisions
< Releases
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
* <strike>[[Release:Release_Automation_on_Mercurial:Starting_a_Release#Locking_slaves | Check to make sure you have all of the different types of slaves that you need]]</strike> | * <strike>[[Release:Release_Automation_on_Mercurial:Starting_a_Release#Locking_slaves | Check to make sure you have all of the different types of slaves that you need]]</strike> | ||
* <strike>[[Release:Release_Automation_on_Mercurial:Preparation#Starting_the_automation | Start the automation]]</strike> | * <strike>[[Release:Release_Automation_on_Mercurial:Preparation#Starting_the_automation | Start the automation]]</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> | ||
* <strike>[[Release:Release_Automation_on_Mercurial:Build#Reset_reserved_slaves | Reset reserved_slaves]]</strike> | * <strike>[[Release:Release_Automation_on_Mercurial:Build#Reset_reserved_slaves | Reset reserved_slaves]]</strike> | ||
| Line 30: | Line 29: | ||
--dryrun localhost:9001 | --dryrun localhost:9001 | ||
* No problems, started the automation by running release sanity again without --dryrun | * No problems, started the automation by running release sanity again without --dryrun | ||
=== Signed Android Builds === | === Signed Android Builds === | ||
Revision as of 18:14, 18 July 2012
Please note that this is NOT a template. You should NOT copy and paste it anywhere. It's only purpose is to provide an example of what build notes could look like when using the checklist. Each release is a unique snowflake and will look slightly differently.
When doing a release you should follow the checklist.
Checklist
Ship the l10n milestoneSet reserved_slavesCheck to make sure you have all of the different types of slaves that you needStart the automationSign Android builds]Reset reserved_slavesPublish FennecRun pushsnip
Notes
Build 1
Started the Release
- Shipped the l10n milestone
- Set "any master", "mozilla-beta", "any builder" for a clobber
- Set reserved slaves to 8
- Verified that bm13 had enough win32, linux, linux64, and r5 lion machines available to it
- Landed config updates, tagged buildbot-configs, buildbotcustom, and tools with {FIREFOX,FENNEC}_14_0b7_{RELEASE,BUILD1}
- Updated and reconfiged the master
- Ran release sanity dry run:
cd /builds/buildbot/build1/master source ../bin/activate PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 14.0b7 --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
- No problems, started the automation by running release sanity again without --dryrun
Signed Android Builds
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
Reset reserved slaves
Reset to 0.
Published Fennec
- Bumped version in http://hg.mozilla.org/build/braindump/raw-file/default/releases-related/push_fennec.sh to 14.0b7
- Ran it:
# ffxbld@stage wget -O push_fennec.sh http://hg.mozilla.org/build/braindump/raw-file/default/releases-related/push_fennec.sh bash push_fennec.sh
- Downloaded multilocale apk (http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/14.0b7/android/multi/fennec-14.0b7.multi.android-arm.apk)
- Browsed to https://market.android.com/publish
- Clicked "Firefox Beta" product
- Clicked "APK Files" tab
- Clicked "Upload APK", uploaded the previously downloaded one.
- Activated the new APK
- Deactivated the previous one
- Clicked "Save"
Pushed beta snippets
cd /opt/aus2/snippets/staging ~/bin/pushsnip Firefox-14.0b99-build1