Build:Release Automation: Difference between revisions

trim current status section, it's in buildnotes now
(remove obsolete instr)
(trim current status section, it's in buildnotes now)
Line 20: Line 20:
=Current status=
=Current status=


For the Firefox 2.0.0.12, we are using Buildbot to drive the release. Instead of a human operater logging into [http://wiki.mozilla.org/index.php?title=Build:Release_Automation#Roles_and_resource_requirements each machine] used in the release process, the machines run Buildbot slaves instead. Most of the slaves simply check out and run Bootstrap, at this point.
This system is used for all current Firefox branches. Public documentation for each release is posted under the "Build" links on the [Releases Releases page].


Both the [http://mxr.mozilla.org/mozilla/source/tools/buildbot-configs/automation/staging/ staging] and [http://mxr.mozilla.org/mozilla/source/tools/buildbot-configs/automation/production production] configs are checked into CVS.
Both the [http://mxr.mozilla.org/mozilla/source/tools/buildbot-configs/automation/staging/ staging] and [http://mxr.mozilla.org/mozilla/source/tools/buildbot-configs/automation/production production] configs are checked into CVS.
There are still several manual processes, which we are working on automating:
* Buildbot config
** if necessary, tag new version of mozilla/tools/release (used RELEASE_AUTOMATION_M7)
*** make sure buildbot-configs/automation/production/master.cfg uses this tag
** need to file bug (e.g. {{Bug|414327}}) and attach diff for bootstrap.cfg (e.g. [http://mxr.mozilla.org/mozilla/source/tools/release/configs/fx-moz18-bootstrap.cfg fx-moz18-bootstrap.cfg])
** need to "cvs update" /home/buildmaster/Automation/buildbot-configs/ and /home/buildmaster/Automation/bootstrap-configs/ after checkin
** need to manually insert passwords into master.cfg, as they are intentionally not in the checked-in version.
** make sure Tinderbox is up-to-date on all slaves {{Bug|397554}}
*** used RELEASE_AUTOMATION_M7 (after tagging mozilla/tools/tinderbox with this)
*** was RELEASE_AUTOMATION_M6_1 before
** reconfig (or restart if idle) buildbot master (<tt>buildbot reconfig `pwd`</tt>), so new automation tag is detected
** ensure that machines have [http://wiki.mozilla.org/Build:Release_Automation#Roles_and_resource_requirements enough resources] {{Bug|393274}}
** cd /data/cltbld/bin and run "cvs up" to update mofo scripts
*** FIXME - these should really be auto-updated and moved to public repo
** kick off buildbot (run as cltbld):
*** buildbot sendchange --master=localhost:9989 -u joduinn -m"Firefox 2.0.0.12 RC1" release
* Tag
** *only applicable for relbranch-based builds* - Bootstrap::Tag::Bump does not handle already-bumped files on relbranch
*** need to make client.mk *_CO_TAGs use MOZILLA_1_8_BRANCH
*** need to add "2.0.0.12pre" tags to version bump files:
**** browser/app/module.ver browser/config/version.txt config/milestone.txt
* Sign
** still manual
** need to sync signed bits manually back to build-console e.g. as cltbld@build-console:
*** rsync -av stage.mozilla.org:/home/ftp/pub/firefox/nightly/2.0.0.12-candidates/ /home/ftp/pub/firefox/nightly/2.0.0.12-candidates/
* Updates
* Stage
** created bouncer links manually {{Bug|414327}}
** created "latest" and "latest-2.0" symlinks manually after final release


=Roles and resource requirements=
=Roles and resource requirements=
canmove, Confirmed users
1,511

edits