1
edit
Changes
Added buildslaves situation
This is the configuration of the http://hera.senecac.on.ca buildbot try server.
== Front Node ==
=== General OS ===
* CentOS 5
* incron
* cron
* perl
* python
* mysql with 1 database set up
* apache configured so that a .cgi/.pl/.py will be run in any directory and the DocumentRoot is writable
* ssh
* vnc
=== CVS-Mirror ===
=== Try-Server ===
* CentOS + LAMP (which DB do you want? versions?) * '''TODO''' -- clarify what we need from http://mxrFTP access to web root.mozilla.org/seamonkey/source/tools/buildbot/buildbot/
* Try-Server web interface requires the REMOTE_USER to be set. We'd like to use .htaccess to manage vs. logins on the box
=== Buildmaster===
* Needs to have port 12345 open to external network. Some of the build slaves will be hosted on the Amazon EC2 service, and will need to access the master on this port. For example, I need to be able to have '''TODOhera.senecac.on.ca:12345'''pointing to the build master.* [http://lxr.mozilla.org/mozilla/source/tools/buildbotcustom/tryserver/ Buildbot custom steps]. (Must be in Build Master directory)
* The master.cfg for Buildbot will be a mixture of these two buildbot-configs ([http://lxr.mozilla.org/mozilla/source/tools/buildbot-configs/tryserver/ TryServer buildbot-config] and [http://lxr.mozilla.org/mozilla/source/tools/buildbot-configs/testing/unittest/ Testing buildbot-config]) but we will end up having to customise it to our Hera farm
== BuildSlaves ==
Behind the hera front node we have the vmlinux1 and the win1, one accessed by VMWare and the other by Remote Desktop.These contain the buildbot slave's in these locations:* vmlinux1** /home/buildslave/slave and /home/buildslave/slave1* X server** buildbot resides on: '''/usr/local/bin/buildbot''NOTE'** buildslave reside on:''' slaves /Users/awdelyea/buildbot/slave'''* win1** ? == BuildSlaves' requirements ===== All Machines ===* Slaves need to be able to communicate to build master on port '''12345'''* Slaves need to be able to talk to the Try-Server (i.e., web server) to push finished builds backvia scp.* '''NOTE2:''' slaves Slaves will have to be able to checkout the latest source code, either from the CVS-mirror that we set up or from Mozilla CVS repository
=== Linux (CentOS 5) ===
python setup.py install
=== Packages OSX ===I don't know if it applies tp write this in here, but * Need VNC access to start build slave. (Something to do with invalid permissions and ssh when building Mozilla on Linux (Ubuntu 7.1) I had to get these packages:* apt-get build-dep firefox* apt-get install build-essential* apt-get install dbus-glib-1-dev* apt-get install libcurl3-dev
