canmove, Confirmed users
1,394
edits
ReleaseEngineering:BuildSlaveSetup: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering:BuildSlaveSetup (view source)
Revision as of 18:03, 4 February 2011
, 4 February 2011→After imaging
(→.) |
|||
| Line 1: | Line 1: | ||
=After imaging= | =After imaging= | ||
Once the | Once a slave has been re-imaged, the [[PostImage]] steps should be completed by IT and other post imaging steps ([[ReleaseEngineering/How To/Set Up a Freshly Imaged Slave]]) done within releng. The slaves should be attached to a staging master. These slaves should be run in this environment to make sure there are no issues with them. They use a special set of staging keys. Before letting the machines bake for a long time, you should ensure that the slave is connected to the staging master. It should also be able to ssh into staging-stage: | ||
ssh -i ~/.ssh/ffxbld_dsa ffxbld@staging-stage.build.mozilla.org | ssh -i ~/.ssh/ffxbld_dsa ffxbld@staging-stage.build.mozilla.org | ||
Once this is done, wait for a number of different types of jobs to cycle as green. If the slave is in good working order, it needs to be moved into production. To do this, you'll need to stop the slave, clobber the slave, change to production ssh keys then modify the buildbot.tac file. | Once this is done, wait for a number of different types of jobs to cycle as green. If the slave is in good working order, it needs to be moved into production. To do this, you'll need to stop the slave, clobber the slave, change to production ssh keys then modify the buildbot.tac file. For that, see [[ReleaseEngineering/How To/Move a Slave Between Production and Staging]]. | ||
=Stopping slave= | =Stopping slave= | ||