Confirmed users
1,018
edits
ReleaseEngineering/How To/Set Up a Freshly Imaged Slave: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Set Up a Freshly Imaged Slave (view source)
Revision as of 21:25, 30 October 2013
, 30 October 2013→Windows 2008 rev2
| Line 13: | Line 13: | ||
* Ensure the slavealloc "basedir" is set to c:\builds\moz2_slave (there is no drive E: on win64-rev2) | * Ensure the slavealloc "basedir" is set to c:\builds\moz2_slave (there is no drive E: on win64-rev2) | ||
* Ensure the build slave is listed in the [http://hg.mozilla.org/build/buildbot-configs/file/bc6077f6ea79/mozilla/production_config.py#l8 WIN64_REV2 slave list] | * Ensure the build slave is listed in the [http://hg.mozilla.org/build/buildbot-configs/file/bc6077f6ea79/mozilla/production_config.py#l8 WIN64_REV2 slave list] | ||
* Ask to have the slave moved to the new Nagios host group via {{bug|920667}} so Nagios doesn't complain about drive E: being missing (there is no drive E: on rev2 machines). | * Ask to have the slave moved to the new Nagios 'w64r2-ix-slaves' host group via {{bug|920667}} so Nagios doesn't complain about drive E: being missing (there is no drive E: on rev2 machines). | ||
= Windows XP (managed) = | = Windows XP (managed) = | ||