Release:Release Automation on Mercurial:Configuration: Difference between revisions

Jump to navigation Jump to search

Release:Release Automation on Mercurial:Configuration (view source)

Revision as of 16:59, 14 June 2012

3,943 bytes removed ,  14 June 2012
no edit summary
No edit summary
Line 208: Line 208:
If you are doing a test release in staging there is [[Release:Release_Automation_on_Mercurial:Documentation#Staging_Specific_Notes|additional setup work]] to do, and the clobberer URL changes.
If you are doing a test release in staging there is [[Release:Release_Automation_on_Mercurial:Documentation#Staging_Specific_Notes|additional setup work]] to do, and the clobberer URL changes.


= 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 />
First log in to the dashboard with your LDAP and then follow the instructions below
==Fennec==
* Click "ship it" to load up the milestone (eg: Fennec 8 Beta Build 2)
* This will take you to a page like [https://l10n.mozilla.org/shipping/confirm-ship?ms=fennec14_beta_b6 https://l10n.mozilla.org/shipping/confirm-ship?ms=fennec14_beta_b6]
* For 14.0b6+ for platforms use
android
* In the 'Add a multi-locale file for' field put
android-multilocale
* select "Add"
** repo: "releases/mozilla-beta"
** branch: "default"
** path: "mobile/android/locales/maemo-locales"
* select "Generate it"
* Copy and paste it into your repo's l10n-changesets_mobile-{version}.json
* go back to the original page
* select "Ship it" to preserve the record of what was shipped
==Firefox==
Note: these instructions also work for Thunderbird.
* Click "ship it" to load up the milestone (eg: Firefox 8 Beta Build 2)
* This will take you to [https://l10n.mozilla.org/shipping/confirm-ship?ms=fx8_beta_b2 https://l10n.mozilla.org/shipping/confirm-ship?ms=fx8_beta_b2]
* Open in a new tab the "l10n-changesets" URL (don't touch any of the other fields) ''record the URL on the build notes''
* copy and paste the list into your l10n-changesets_mozilla-{version}
* go back to the original page
* 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>
= Starting the automation =
Generally, the workflow for kicking off Release Automation is as follows:
* Update the configuration files
* Tag buildbotcustom <small>''(branch <tt>production-0.8</tt>)''</small>, buildbot-configs <small>''(branch <tt>production</tt>)''</small>, tools <small>''(branch <tt>default</tt>)''</small> with the correct _RELEASE and _BUILDn tags. You must use FIREFOX_${VERSION}_BUILDn and FIREFOX_${VERSION}_RELEASE for Firefox releases, FENNEC_${VERSION}_BUILDn and FENNEC_${VERSION}_RELEASE for Fennec releases, or all 4 tags for combined releases.
* Update the Buildbot Master doing the release
* Run the pre-flight sanity check. This is done in the master directory (watch out for PYTHONPATH). For example:
# Combined release
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 6.0b2 --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
# Firefox-only release
cd /builds/buildbot/build1/master
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 6.0b2 --branch mozilla-beta --build-number 1 \
  --release-config release-firefox-mozilla-beta.py --products firefox  \
  --dryrun localhost:9001
* Start the automation by running the sanity script again, without --dryrun. For example:
# buildbot should in in $PATH, source ve env
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u rail \
  -V 6.0b2 --branch mozilla-beta --build-number 1 \
  -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py --products firefox,fennec localhost:9001
If you're working in staging you must make sure to pass in the correct staging release config (staging_release-firefox-<branch name>.py)
If for some reason you need to perform the sendchange manually, here's a sample. Note that the branch name is the repo path to the source repository. In staging, this will be a user repo. All parameters are required:</p>
buildbot sendchange --username bhearsum --master localhost:9010 --branch releases/mozilla-release \
    -p script_repo_revision:FIREFOX_3_6_12_RELEASE -p products:firefox,fennec release_build


= Tree Merges (release driver) =
= Tree Merges (release driver) =
Bhearsum
canmove, Confirmed users
6,441

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/441380"

Navigation menu