ReleaseEngineering/TryserverAsBranch: Difference between revisions
Lukasblakk (talk | contribs) |
Lukasblakk (talk | contribs) |
||
| Line 9: | Line 9: | ||
Added TRY_SLAVES to config, copied those into c['slaves'] in master-main.cfg | Added TRY_SLAVES to config, copied those into c['slaves'] in master-main.cfg | ||
Took out slavePortnum and http listening port in master-main.cfg in try-trunk-master | Took out slavePortnum and http listening port in master-main.cfg in try-trunk-master | ||
==New upload location== | |||
Builds & crashreporter-symbols will now be uploaded to ftp.m.o/mozilla.org/firefox/tryserver-builds | |||
Symbols for win32 will still go to build.mozilla.org | |||
==Dry run with a tryserver slave from production pool== | ==Dry run with a tryserver slave from production pool== | ||
Moving try-w32-slave20 out of sandbox and into build network to test uploads | |||
==Update Nagios== | ==Update Nagios== | ||
Will need to use start_buildbot.sh, so adjust nagios accordingly to watch for 2 twistd procs. | Will need to use start_buildbot.sh, so adjust nagios accordingly to watch for 2 twistd procs. | ||
==Update Cron== | ==Update Cron== | ||
Revision as of 23:07, 5 May 2010
What's this about?
This page documents the moving of tryserver from being on its own master, with separate code from the release automation, to becoming another branch in the configs of the release automation. The main bug 520227 tracks the progress of this endeavor.
The Rollout
Backing up the current setup
The changeset (c7705d122890) of the current buildbotcustom code was tagged to ensure that we could keep that tryserver running at the same time as starting up the new master.
Set up a new master
On pm02, a new master was created with the only active branch being tryserver. Added TRY_SLAVES to config, copied those into c['slaves'] in master-main.cfg Took out slavePortnum and http listening port in master-main.cfg in try-trunk-master
New upload location
Builds & crashreporter-symbols will now be uploaded to ftp.m.o/mozilla.org/firefox/tryserver-builds Symbols for win32 will still go to build.mozilla.org
Dry run with a tryserver slave from production pool
Moving try-w32-slave20 out of sandbox and into build network to test uploads
Update Nagios
Will need to use start_buildbot.sh, so adjust nagios accordingly to watch for 2 twistd procs.