ReferencePlatforms/Win32: Difference between revisions

Line 493: Line 493:
(We followed tips outlined [http://www.windowsdevcenter.com/pub/a/windows/2005/02/08/NTFS_Hacks.html http://www.windowsdevcenter.com/pub/a/windows/2005/02/08/NTFS_Hacks.html] and [http://technet.microsoft.com/en-us/library/cc785435.aspx http://technet.microsoft.com/en-us/library/cc785435.aspx].)
(We followed tips outlined [http://www.windowsdevcenter.com/pub/a/windows/2005/02/08/NTFS_Hacks.html http://www.windowsdevcenter.com/pub/a/windows/2005/02/08/NTFS_Hacks.html] and [http://technet.microsoft.com/en-us/library/cc785435.aspx http://technet.microsoft.com/en-us/library/cc785435.aspx].)


== RelEng stuff ==
== Releng stuff ==
 
=== verify setup in staging ===
== Setup Slave ==
 
Login as cltbld
 
mkdir /e/builds
 
...and either run
/d/mozilla-build/python25/scripts/buildbot create-slave moz2_slave <hostname>:<port> <slave_name> <password>
 
or else copy over the buildbot.tac and info files from another win32 slave.
 
Make sure the buildbot.tac file has:
* <tt>umask = 002</tt> instead of None, so that nightly update snippets have sensible permissions
* <tt>keepalive = None</tt> so that a busy master doesn't cause us to timeout jobs
* <tt>usepty = 1</tt> so we can kill off failed unit test runs (definitely need this on mac and linux, not sure about win32 but here for parity)
 
== Start Slave ==
$ cd
$ /d/mozilla-build/python25/scripts/buildbot start /e/builds/moz2_slave
 
'''Note: make sure to minimize the MSYS window, or else unittests will fail... {{bug|465096}}
 
== verify setup in staging ==
* trigger a build on staging-master, to make sure all works ok
* trigger a build on staging-master, to make sure all works ok


== switchover from staging to production ==
=== switchover from staging to production ===
* stop slave process
* stop slave process
* switchover the .ssh keys to use production keys
* switchover the .ssh keys to use production keys
canmove, Confirmed users
6,441

edits