Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
No edit summary |
|||
| Line 176: | Line 176: | ||
== Post-Imaging Steps == | == Post-Imaging Steps == | ||
Note: I haven't done those yet, as I didn't want to "pollute" the reference image with this | |||
=== Config I'm Not Sure About === | |||
This is either "probably MoCo-specific" or stuff I'm not sure we need on Parallels, see [[ReferencePlatforms/Mac-10.5]] for the details on those. | |||
* Nagios (probably MoCo-specific) | |||
* ntp config (not sure if needed with Parallels) | |||
* chown scripts (still needed with hg/buildbot setups?) | |||
=== Build User setup === | |||
Set up a user for cltbld/seabld, and perform the following steps on it: | |||
==== Environment Variables ===== | |||
Add the appropriate paths to the Buildbot user's .profile | |||
echo 'export PYTHONHOME="/tools/python"' >> ~/.profile | |||
echo 'export PYTHONPATH="/tools/buildbot/lib/python2.5/site-packages:/tools/twisted/lib/python2.5/site-packages:/tools/twisted-corelib/python2.5/site-packages/:/tools/zope-interface/lib/python2.5/site-packages/"' >> ~/.profile | |||
echo 'export PATH="/opt/local/bin:/tools/buildbot/bin:/tools/twisted/bin:/tools/twisted-core/bin:$PYTHONHOME/bin:$PATH"' >> ~/.profile | |||
==== SSH Keys ===== | |||
Copy ssh keys for the user from another box where it's set up into ~/.ssh/ | |||
== Establish initial ssh connections and accept keys == | |||
Execute the following simple ssh calls to connect to the ftp server (stage), symbol server (if different from ftp), and update server so that the various pieces of the build can be uploaded automatically by the build scripts when needed: | |||
ssh seabld@stage.mozilla.org pwd | |||
ssh seabld@aus2-community.mozilla.org pwd | |||
ssh seabld@hg.mozilla.org | |||
ssh seabld@dm-symbolpush01.mozilla.org pwd | |||
(or equivalent for whatever servers you need to access) | |||
== Setup buildbot slave == | |||
Remove any /builds/*slave* left over on the image then | |||
mkdir -p /builds/slave | |||
cd /builds/slave | |||
and either | |||
* run "buildbot create-slave" with appropriate arguments to point at the staging-master. Note that we need to set "umask = 002" in buildbot.tac. | |||
* or else copy over buildbot.tac and info files from another staging slave and update the slavename and basedir | |||
Using a VNC session rather than ssh, start the slave with | |||
buildbot start /builds/slave | |||
edits