Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Release Automation: Difference between revisions
→Starting the automation
(Created page with 'The SeaMonkey 2 release automation process builds upon Mozilla's Mercurial-based release automation by reusing the gener...') |
|||
| Line 32: | Line 32: | ||
=== 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 [http://hg.mozilla.org/ | # Update [http://hg.mozilla.org/users/kairo_kairo.at/bbconf-sm2/file/tip/l10n-changesets l10n-changesets] (normally performed by someone from the l10n team days ahead of time) | ||
# Update [http://hg.mozilla.org/ | # Update [http://hg.mozilla.org/users/kairo_kairo.at/bbconf-sm2/file/tip/release_config.py release_config.py] | ||
# Reconfigure the buildbot master | # Reconfigure the buildbot master | ||
# Kick-off automation with the following command: | # Kick-off automation with the following command: | ||
buildbot sendchange --username= | buildbot sendchange --username=kairo --master=localhost:9010 --branch=users/kairo_kairo.at/comm-central -m "SeaMonkey 2.0a4build1" doit | ||
Of course, replacing username, branch, and the message appropriately. '''Be sure not to leave out --branch.''' | Of course, replacing username, branch, and the message appropriately. '''Be sure not to leave out --branch.''' | ||
== Steps == | == Steps == | ||