[146829] contrib/buildbot-test/README.md
raimue at macports.org
raimue at macports.org
Fri Mar 18 10:16:18 PDT 2016
Revision: 146829
https://trac.macports.org/changeset/146829
Author: raimue at macports.org
Date: 2016-03-18 10:16:18 -0700 (Fri, 18 Mar 2016)
Log Message:
-----------
How to set up both master and slave on localhost
This setup is only intended for development and runs both master and slave on
the same machine. Instructions for production systems are still missing.
Modified Paths:
--------------
contrib/buildbot-test/README.md
Modified: contrib/buildbot-test/README.md
===================================================================
--- contrib/buildbot-test/README.md 2016-03-18 17:14:44 UTC (rev 146828)
+++ contrib/buildbot-test/README.md 2016-03-18 17:16:18 UTC (rev 146829)
@@ -1,49 +1,144 @@
# Hacking on the MacPorts buildbot
+## Setting up both buildbot master and slave for testing on localhost
-## Setting up a buildbot master for testing
+These steps explain how to install buildbot locally for hacking on the infrastructure. This will run both the buildbot master and buildbot slave on localhost. Note the buildbot slave will run in a non-default prefix, to avoid interfering with your installation in /opt/local.
-### 1. Install buildbot
+### Setting up buildbot master on localhost
+#### 1. Install buildbot
+
sudo port install buildbot
-### 2. Create new directory for buildbot configuration
- buildbot create-master ~/buildbot-master
+#### 2. Create new directory with buildbot master configuration
-### 3. Add and edit sample configuration files
+ sudo mkdir -p /opt/mp-buildbot
+ sudo chown -R $USER:buildbot /opt/mp-buildbot
+ sudo chmod -R 775 /opt/mp-buildbot
- cd ~/buildbot-master
+ buildbot create-master /opt/mp-buildbot/master
+
+
+#### 3. Add and edit sample configuration files
+
+ cd /opt/mp-buildbot/master
ln -s .../path/to/contrib/buildbot-test/master.cfg
cp .../path/to/contrib/buildbot-test/config.json.sample config.json
cp .../path/to/contrib/buildbot-test/slaves.json.sample slaves.json
Check settings in config.json and adapt as needed.
-### 4. Set up authentication
- cd ~/buildbot-master
+#### 4. Set up authentication
+
+ cd /opt/mp-buildbot/master
htpasswd -c -d ./htpasswd admin
-### 5. Starting buildbot
+#### 5. Starting buildbot
+
To start buildbot, execute the `start` command. The OS X firewall will request you to allow access for Python. Then you can view the buildbot instance in your web browser.
- buildbot start ~/buildbot-master
+ buildbot start /opt/mp-buildbot/master
open http://localhost:8010/
-### 5. Testing changes
+#### 5. Testing changes
+
After making any changes to `master.cfg`, you can reload the configuration with the `reconfig` command. This is faster than doing a full `restart`. In a similar way, you can completely `stop` the buildbot.
- buildbot reconfig ~/buildbot-master
+ buildbot reconfig /opt/mp-buildbot/master
- buildbot restart ~/buildbot-master
+ buildbot restart /opt/mp-buildbot/master
- buildbot stop ~/buildbot-master
+ buildbot stop /opt/mp-buildbot/master
+### Setting up buildbot slave on localhost
-## Setting up a buildbot slave
+This will use your copy of MacPorts in /opt/local for all tooling, but actual builds on the slave will be made in a separate prefix. Make sure this installation provides an up-to-date ports tree.
+
+#### 1. Install MacPorts into a new prefix
+
+You need to use a new prefix for this installation. These instructions will use `/opt/mp-buildbot/prefix`.
+
+You will have to install this from source following
+
+* https://guide.macports.org/#installing.macports.source.multiple
+
+
+#### 2. Install buildbot-slave
+
+Install buildbot-slave in your *normal* `/opt/local` prefix:
+
+ sudo port install buildbot-slave
+
+
+#### 3. Create new directory with buildbot slave configuration
+
+Create a directory that will contain the buildslaves working directory.
+
+ sudo mkdir -p /opt/mp-buildbot
+ sudo chown -R $USER:buildbot /opt/mp-buildbot
+ sudo chmod -R 775 /opt/mp-buildbot
+
+Create two buildslaves, one for base running as the buildbot user, one for ports running as root:
+
+ OSXVERS=$(sw_vers -productVersion | grep -oE '^[0-9]+\.[0-9]+')
+ ARCH=$(uname -m)
+ PASSWORD=... # add your password here
+
+ sudo -H -u buildbot buildslave \
+ create-slave --umask 022 \
+ /opt/mp-buildbot/slave-base \
+ localhost:9989 \
+ base-$OSXVERS-$ARCH \
+ $PASSWORD
+
+ sudo -H buildslave \
+ create-slave --umask 022 \
+ /opt/mp-buildbot/slave-ports \
+ localhost:9989 \
+ ports-$OSXVERS-$ARCH \
+ $PASSWORD
+
+#### 3. Add new builldbot slaves to buildbot master configuration
+
+Add the buildslaves to your buildmaster's master.cfg using the password you provided when creating them. Then reload the buildbot master configuration.
+
+ $EDITOR /opt/mp-buildbot/master/slaves.json
+
+XXX: edit build\_platforms in master.cfg
+
+IMPORTANT! Change the following configuration options in config.json:
+
+ $EDITOR /opt/mp-buildbot/master/config.json
+
+> "slaveprefix": "/opt/mp-buildbot/prefix"
+> "toolsprefix": "/opt/local"
+
+Reconfigure the buildbot master:
+
+ buildbot reconfig /opt/mp-buildbot/master
+
+
+#### 4. Start the two buildslaves
+
+These commands start the new build slaves. They should connect to the master successfully and be visible in the webinterface.
+
+ sudo -H -u buildbot buildslave start /opt/mp-buildbot/slave-base
+ sudo -H buildslave start /opt/mp-buildbot/slave-ports
+
+
+#### 5. Test your first build
+
TODO
+
+
+## Setting up buildbot master and slaves for production
+
+These instructions explain how to install buildbot in a production environment, in which master slaves run on different machines to produce MacPorts packages.
+
+TODO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-changes/attachments/20160318/dcd0a0ab/attachment-0001.html>
More information about the macports-changes
mailing list