ReleaseEngineering/TryserverAsBranch

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, try-linux-slave08, try-mac-slave13 out of sandbox and into build network to test uploads

• Setup for w32 as per ReferencePlatforms/Win32#Manual_Setup_Steps_after_VMImage (production)

Update Nagios

Will need to use start_buildbot.sh, so adjust nagios accordingly to watch for 2 twistd procs.