Charm: buildbot-slave
Summary
system to automate the compile/test cycle
Charm Store
juju deploy cs:~yellow/oneiric/buildbot-slave-5
Owner
yellow
Series
oneiric
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.
Links
Repository   Bugs
lp:~yellow/charms/oneiric/buildbot-slave/trunk
Interfaces
Provides
Requires
Config
script-args string
script-retrieval-method string
script-path string
installdir string
buildbot-pkg string
extra-repository string
extra-packages string
script-source string
script-url string
builders string
Details
Readme
Usage
=====

This charm expects to work with the buildbot-master charm.  Please see
that charm's README for example usage, and see the examples directory
in this charm for an example configuration.  This charm expects
configuration to be done primarily at deploy time.

Running the charm tests
=======================

1) Establish a charm repository if you do not already have one.  A charm
   repository is a directory with subdirectories for each Ubuntu version being
   used.  Inside those per-Ubuntu-version directories are the charm
   directories.  For example, to make a charm repository for this charm under
   Oneiric follow these steps:

    a) mkdir -p ~/juju-charms/oneiric
    b) ln -s `pwd` ~/juju-charms/oneiric/buildbot-slave

2) Copy the juju_wrapper file into some place earlier in your PATH than the
   real juju executable, naming it "juju".  Edit the CHARM_TEST_REPO variable
   therein to reflect the location of the charm repo from step 1.

3) Bootstrap the juju environment if not already done:

    juju bootstrap

4) Run the tests: RESOLVE_TEST_CHARMS=1 tests/buildbot-slave.test


Running the charm helper tests
==============================

Just run "python hooks/tests.py".
Changes  
2012/07/25 Francesco Banconi [r=bac] Update lpsetup command line arguments. (revno 31)
2012/05/22 Francesco Banconi [r=gary] Fixed a typo in the lpbuildbot configuration file. (revno 30)
2012/05/22 Francesco Banconi [r=gary] Updated dependencies path in lpbuildbot configuration file. (revno 29)
2012/05/10 Francesco Banconi [r=gary] Use lpsetup in place of setuplxc to create the launchpad testing environment (revno 28)
2012/04/16 Francesco Banconi [r=gary] Only install replacement sources in charms if return code is 100. (revno 27)
2012/04/05 Brad Crittenden [r=gary] If the first call to apt-get has an error, rewrite /etc/apt/sources.list to use standard re (revno 26)
2012/03/23 Francesco Banconi [r=gary] Updated setuplxc args to include the random/urandom hack. (revno 25)
2012/03/20 Brad Crittenden [r=bac] Use new spelling for python-shelltoolbox. (revno 24)
2012/03/10 Gary Poster [r=benji] add extra-packages option (revno 23)
Lint Check
  • err: Charms need a maintainer (See RFC2822) - Name <email>
  • warn: missing recommended hook start
  • warn: missing recommended hook stop

In other archives
oneiric/buildbot-slave
~gary:oneiric/buildbot-slave
~frankban:oneiric/buildbot-slave