1
edit
Changes
m
NOTE2: The Mac slave has the slave in /opt/slave and it is owned by armenzg account, <span style="color:red; font-weight:bold">shall we create a "buildslave" account to own it?</span>
* MAC
** /usr/local/bin/buildbot create-slave /opt/slave hera:12345 mac1 mac1
* MAC
** /usr/local/bin/buildbot start /opt/slave
* MAC
** /usr/local/bin/buildbot restart /Users/adam.delyea/buildbot/slave
Fixed issues with mac
* To connect to the tryserver do it through ssh to hera.senecac.on.ca
* The folders "cgi-bin", "html" and "patches" are '''aliased''' to show to the public
* The "data" folder is aliased to /home/buildreturn/data
== Master (Front node) ==
* The basedir of the buildbot is the home directory, therefore "buildobt restart ."
* Run "perl process_changes_test.pl" to read the patches from the "tryserver" and notify of changes to the master. Every 2 minutes a cronjob takes care of running this command. Patches get copied from /home/tryserver/patches to "/home/buildmaster/patches" or "patches_test" (this may be unified later onIn our setup, the tryserver and the buildmaster live in the same server)
== Slaves ==
NOTE: For any account credentials talk with Dave Humphrey<br />
=== Connecting ===
'''NOTE:''' Make sure that the tryserver has in ~/.ssh/authorized_keys the keys of the slaves in it AND make sure that you ssh at least once to the tryserver from the slave so you can have the RSA fingerprint of the "tryserver" in your slave's ~/.ssh/know_hosts
* LINUX& MAC
** buildbot create-slave slave hera:12345 lin1 lin1
* WINDOWS
** Run c:\mozilla-build\start-msvc8.bat to start
=== Start ===
* LINUX& MAC
** buildbot start ~/slave
* WINDOWS ("twistd.pid" does not get created)
** Open MozBuild
** /c/Python24/scripts/buildbot start /c/slave/ &//make note of the ampersand symbol, it puts the task in the background
=== Restart ===
* LINUX& MAC
** buildbot restart ~/slave
* WINDOWS - '''Kill it and then start it again since twistd.pid has not been generated'''
** ps aux
== Fixed ==
* Created mac slave under the home folder of the buildslave account instead of previous location
* Add the ssh keys to the '''tryserver''' account, '''the public keys of each slave is under .ssh on the tryserver'''
* The SCP_STRING points to "data" on the "tryserver" account which is an alias to "data" on "buildreturn" account
