Confirmed users
502
edits
ReleaseEngineering/How To/Set Up a Freshly Imaged Slave: Difference between revisions
ReleaseEngineering/How To/Set Up a Freshly Imaged Slave (view source)
Revision as of 03:06, 16 July 2014
, 16 July 2014→Windows (GPO)
| Line 14: | Line 14: | ||
** try/build(prod) machines now have their ssh keys copied via GPO. Simply enable in slavealloc. | ** try/build(prod) machines now have their ssh keys copied via GPO. Simply enable in slavealloc. | ||
** It is worth verifying that the keys are set up correctly as this is relatively new (july 15, 2014) | ** It is worth verifying that the keys are set up correctly as this is relatively new (july 15, 2014) | ||
** staging keys are | ** '''staging keys are not setup via GPO.''' they either will have no keys or they will be given prod keys. Either way, you need to cp keys from another staging slave to the freshly imaged one via [https://wiki.mozilla.org/ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave#Staging setup staging ssh keys] | ||
* Test slaves | * Test slaves | ||
** Host names: t-xp32-ix, t-w732-ix, t-w864-ix | ** Host names: t-xp32-ix, t-w732-ix, t-w864-ix | ||
** No additional steps needed. Simply enable on slavealloc | ** No additional steps needed. Simply enable on slavealloc | ||