THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
And create a user account to run the slave as, then set up the slave:
| No Format |
|---|
sudo useradd -c "SpamAssassin Buildbot" buildbot
sudo su - buildbot
mkdir -p /home/buildbot/slaves
[now, you need the buildbot password. ask on the IRC channel
and one of the PMC should be able to set you up with one.
If you're a PMC member, take a look at /home/buildbot/README
on bugzilla.]
|
Commands to create a new buildbot slave
You need a buildbot password be set up for you – a random string in a file in
/home/buildbot/pwds/. ask on the IRC channel and one of the PMC should be able to set you up with one.
| No Format |
|---|
PASSWORD=[password] NAME=t-sol10-561 [give your slave a good name, like "jm-debian-stable" or "jm-ubuntu-hoary-perl585"] HOST_OS="username-hostname-osname" mkdir sudo mkdir -p /home/buildbot/slaves/$NAME sudo chown buildbot /home/buildbot/slaves/$HOST_OS$NAME cd /home/buildbot/slaves/$HOST_OS $NAME sudo su buildbot -c \ "mktap buildbot slave --basedir /home/buildbot/slaves/$HOST_OS --master $NAME \ --master buildbot.spamassassin.org:9989 --name $HOST_OS$NAME \ --passwd $PASSWORD --usepty 0 --keepalive 300 |
(note: use "mktap" directly instead of "buildbot slave so you can set usepty and keepalive.) Mail dev/at/SpamAssassin.apache.org the $HOST_OS string you've chosen.
=0"
|
on the zoneWith buildbot 0.6.6, you don't need to run "mktap" directly and should run this command:
| No Format |
|---|
echo $PASSWORD > $HOME/pwd sudo mv $HOME/pwd /home/buildbot slave --usepty 0 --keepalive 300/pwds/$NAME sudo chown buildbot /home/buildbot/pwds/$NAME sudo chmod 600 /home/sabuildbotbuildbot/slaves/$HOST_OS \pwds/$NAME sudo vi /home/buildbot/bots/buildbot/master.cfg [add new lines/entries for $NAME] sudo vi buildbot.spamassassin.org:9989 $HOST_OS $PASSWORD/etc/init.d/buildbot [add new lines/entries for $NAME, if it's running on the zone] |
Command to start the slave process:
...