Release:Release Automation on Mercurial:Starting a Release: Difference between revisions

Jump to navigation Jump to search

Release:Release Automation on Mercurial:Starting a Release (view source)

Revision as of 17:19, 14 June 2012

578 bytes removed ,  14 June 2012
→‎Starting the automation
No edit summary
Line 42: Line 42:
= Starting the automation =
= Starting the automation =
Generally, the workflow for kicking off Release Automation is as follows:
Generally, the workflow for kicking off Release Automation is as follows:
* Update the configuration files
* For build1 only, create a symlink to the candidates directory (until {{bug|725839}} is resolved). For example:
* 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.
# ffxbld or tbirdbld@stage
* Update the Buildbot Master doing the release
version=13.0b6
* Run the pre-flight sanity check. This is done in the master directory (watch out for PYTHONPATH). For example:
product=thunderbird
cd /pub/mozilla.org/$product/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
* Land configuration file updates
* 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. For example, FENNEC_14_0b6_RELEASE and FENNEC_14_0b6_BUILD1. Multiple production releases require tags for both products.
* Update & reconfig the master doing the release
* Run release sanity. For example:
  # Combined release
  # Combined release
  cd /builds/buildbot/build1/master
  cd /builds/buildbot/build1/master
Line 57: Line 64:
   --release-config release-firefox-mozilla-beta.py --products firefox  \
   --release-config release-firefox-mozilla-beta.py --products firefox  \
   --dryrun localhost:9001
   --dryrun localhost:9001
* Start the automation by running the sanity script again, without --dryrun. For example:
* Start the automation by running the sanity script again, without --dryrun.
# 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 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
Bhearsum
canmove, Confirmed users
6,439

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/441394"

Navigation menu