Confirmed users
1,364
edits
Release:Release Automation on Mercurial:Documentation: Difference between revisions
Jump to navigation
Jump to search
Release:Release Automation on Mercurial:Documentation (view source)
Revision as of 22:46, 6 April 2012
, 6 April 2012→Starting the automation
| Line 277: | Line 277: | ||
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 | * Update the configuration files | ||
* Tag buildbotcustom, buildbot-configs, tools | * 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 | * 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: | * Run the pre-flight sanity check. This is done in the master directory (watch out for PYTHONPATH). For example: | ||