Confirmed users
4,467
edits
(→.) |
|||
| Line 1: | Line 1: | ||
= | =After imaging= | ||
Once the slaves have been brought up and had [[PostImage]] steps done and other post imaging steps from their respective reference platform document, they will (hopefully) attach to staging-master:9010. 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: | Once the slaves have been brought up and had [[PostImage]] steps done and other post imaging steps from their respective reference platform document, they will (hopefully) attach to staging-master:9010. 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. | ||
=Stopping slave= | =Stopping slave= | ||