yellow team mailing list archive

[Gary Poster <gary.poster@xxxxxxxxxxxxx>]

Gary Poster has proposed merging lp:~gary/charms/oneiric/buildbot-slave/trunk into lp:~yellow/charms/oneiric/buildbot-slave/trunk.

Requested reviews:
  Gary Poster (gary)

For more details, see:
https://code.launchpad.net/~gary/charms/oneiric/buildbot-slave/trunk/+merge/90764

Re-landing of lp:~frankban/charms/oneiric/buildbot-slave/initial so that it can merge with trunk.  See https://code.launchpad.net/~frankban/charms/oneiric/buildbot-slave/initial/+merge/90739 for real review.
-- 
https://code.launchpad.net/~gary/charms/oneiric/buildbot-slave/trunk/+merge/90764
Your team Launchpad Yellow Squad is subscribed to branch lp:~yellow/charms/oneiric/buildbot-slave/trunk.

=== added file 'config.yaml'
--- config.yaml	1970-01-01 00:00:00 +0000
+++ config.yaml	2012-01-30 19:13:27 +0000
@@ -0,0 +1,17 @@
+options:
+  installdir:
+    description: |
+      The directory where the Buildbot slave will be installed.
+    type: string
+    default: /tmp/buildbot
+  name:
+    description: |
+      The name of this slave.
+    type: string
+    default: example-slave
+  passwd:
+    description: |
+      The password of this slave.
+    type: string
+    default: pass
+

=== added directory 'hooks'
=== added file 'hooks/buildbot-relation-changed'
--- hooks/buildbot-relation-changed	1970-01-01 00:00:00 +0000
+++ hooks/buildbot-relation-changed	2012-01-30 19:13:27 +0000
@@ -0,0 +1,18 @@
+#!/bin/bash
+# This must be renamed to the name of the relation. The goal here is to
+# affect any change needed by relationships being formed, modified, or broken
+# This script should be idempotent.
+juju-log $JUJU_REMOTE_UNIT modified its settings
+
+BUILDBOT_DIR=`config-get installdir`
+NAME=`config-get name`
+PASSWD=`config-get passwd`
+HOST=`relation-get private-address`
+
+juju-log "--> create slave"
+buildslave create-slave $BUILDBOT_DIR $HOST $NAME $PASSWD
+juju-log "<-- create slave"
+
+juju-log "--> start"
+buildslave start $BUILDBOT_DIR
+juju-log "<-- start"

=== added file 'hooks/config-changed'
--- hooks/config-changed	1970-01-01 00:00:00 +0000
+++ hooks/config-changed	2012-01-30 19:13:27 +0000
@@ -0,0 +1,2 @@
+#!/bin/bash
+# Hook for handling config changes.

=== added file 'hooks/install'
--- hooks/install	1970-01-01 00:00:00 +0000
+++ hooks/install	2012-01-30 19:13:27 +0000
@@ -0,0 +1,10 @@
+#!/bin/bash
+# Here do anything needed to install the service
+# i.e. apt-get install -y foo  or  bzr branch http://myserver/mycode /srv/webroot
+set -eux # -x for verbose logging to juju debug-log
+
+juju-log "--> install"
+BUILDBOT_DIR=`config-get installdir`
+apt-get install -y buildbot
+mkdir -p $BUILDBOT_DIR
+juju-log "<-- install"

=== added file 'hooks/start'
--- hooks/start	1970-01-01 00:00:00 +0000
+++ hooks/start	2012-01-30 19:13:27 +0000
@@ -0,0 +1,5 @@
+#!/bin/bash
+# Here put anything that is needed to start the service.
+# Note that currently this is run directly after install
+# i.e. 'service apache2 start'
+

=== added file 'hooks/stop'
--- hooks/stop	1970-01-01 00:00:00 +0000
+++ hooks/stop	2012-01-30 19:13:27 +0000
@@ -0,0 +1,7 @@
+#!/bin/bash
+# This will be run when the service is being torn down, allowing you to disable
+# it in various ways..
+# For example, if your web app uses a text file to signal to the load balancer
+# that it is live... you could remove it and sleep for a bit to allow the load
+# balancer to stop sending traffic.
+# rm /srv/webroot/server-live.txt && sleep 30

=== added file 'metadata.yaml'
--- metadata.yaml	1970-01-01 00:00:00 +0000
+++ metadata.yaml	2012-01-30 19:13:27 +0000
@@ -0,0 +1,21 @@
+name: buildbot-slave
+summary: system to automate the compile/test cycle
+description: |
+  The BuildBot is a system to automate the compile/test cycle required by
+  most software projects to validate code changes. By automatically
+  rebuilding and testing the tree each time something has changed, build
+  problems are pinpointed quickly, before other developers are
+  inconvenienced by the failure. The guilty developer can be identified
+  and harassed without human intervention.  By running the builds on a
+  variety of platforms, developers who do not have the facilities to
+  test their changes everywhere before checkin will at least know
+  shortly afterwards whether they have broken the build or not. Warning
+  counts, lint checks, image size, compile time, and other build
+  parameters can be tracked over time, are more visible, and are
+  therefore easier to improve.
+requires:
+  buildbot:
+    interface: master
+provides:
+  buildbot:
+    interface: slave

=== added file 'revision'
--- revision	1970-01-01 00:00:00 +0000
+++ revision	2012-01-30 19:13:27 +0000
@@ -0,0 +1,1 @@
+18