Rev 47: Start defining karmic slave. in file:///home/vila/buildbot/bzr/

[Vincent Ladeuil]

At file:///home/vila/buildbot/bzr/

------------------------------------------------------------
revno: 47
revision-id: v.ladeuil+lp at free.fr-20090810164912-586wgs4973wavu85
parent: v.ladeuil+lp at free.fr-20090810164730-ywr53y0n3vf0wk4l
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: bzr
timestamp: Mon 2009-08-10 18:49:12 +0200
message:
  Start defining karmic slave.
  
  * slaves/karmic/Makefile: 
  Should be ok for karmic (based on hardy).
  
  * README: 
  Add karmic instructions.
-------------- next part --------------
=== modified file 'README'
--- a/README	2009-08-10 08:30:57 +0000
+++ b/README	2009-08-10 16:49:12 +0000
@@ -126,6 +126,25 @@
   With that in place, the slave can only connect to the build
   master via the ssh tunnel.
 
+* karmic 64 bits slave created with
+
+    mkdir -p slaves/karmic
+    buildbot create-slave slaves/larmic localhost:9989 hardy heron
+
+  Note that we use an ssh tunnel to forward the connection to the
+  build master (see below) so we appear to connect locally.
+
+* setting up the env for karmic
+
+  We copied hardy setup without any sham, so look there for
+  details not repeated here.
+
+    @reboot ssh -L 9989:localhost:9989 <user at master> -p <master_port> -N
+    @reboot make -C ~/buildbot/bzr/slaves/karmic start
+
+  <user at master> should be defined between master and slave
+  administrators.
+
 * w2003x64 created with:
 
     buildbot create-slave slaves/w2003x64 locahost:9989 w2003x64 w2003x64

=== modified file 'TODO'
--- a/TODO	2009-08-10 16:47:30 +0000
+++ b/TODO	2009-08-10 16:49:12 +0000
@@ -1,11 +1,3 @@
-* Switch to a configuration where a dedicated user is responsible
-   for the master and/or the slave
-
-* Use ssh tunnels (local port forwarding) to address security
-   issues (using passwords is really poor from a security point
-   of view since they are send in clear text and we want to
-   archive the whole master.cfg anyway)
-
 * Allows python module to be imported in master.cfg (this can
    work today if all buildbot commands are issued in the master
    directory but we'd like a better way relying on PYTHONPATH)

=== modified file 'master/master.cfg'
--- a/master/master.cfg	2009-08-10 16:14:53 +0000
+++ b/master/master.cfg	2009-08-10 16:49:12 +0000
@@ -23,6 +23,7 @@
 c['slaves'] = [
     BuildSlave('hardy', 'heron'),
     BuildSlave('jaunty', 'jackalope'),
+    BuildSlave('karmic', 'koala'),
     BuildSlave('tiger', 'tiger'),
     BuildSlave('leopard', 'leopard'),
     BuildSlave('w2003x64', 'w2003x64'),

=== added directory 'slaves/karmic'
=== added file 'slaves/karmic/Makefile'
--- a/slaves/karmic/Makefile	1970-01-01 00:00:00 +0000
+++ b/slaves/karmic/Makefile	2009-08-10 16:49:12 +0000
@@ -0,0 +1,25 @@
+# -*- makefile -*-
+
+# Set the environment 
+
+# ${HOME}/bin for slave specific versions
+# /bin for kill
+# /usr/bin for bzr, make, python, tail, twistd
+export PATH=${HOME}/bin:/bin:/usr/bin
+# ${HOME}/lib/python for slave specific versions
+#     (including testtools and subunit for selftest --parallel=fork)
+export PYTHONPATH=${HOME}/lib/python
+
+start:
+	twistd --no_save -y buildbot.tac
+
+stop:
+	kill `cat twistd.pid`
+
+# start will be issued even if stop fails
+restart:
+	-${MAKE} stop
+	${MAKE} start
+
+log:
+	tail -f twistd.log