Charm: buildbot-slave
Summary
system to automate the compile/test cycle
system to automate the compile/test cycle
Charm Store
juju deploy cs:precise/buildbot-slave-0
juju deploy cs:precise/buildbot-slave-0
Series
precise
precise
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.
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.
Hooks
Config
script-args string
script-retrieval-method string
script-path string
installdir string
buildbot-pkg string
extra-repository string
extra-packages 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/03/12 Mark Mims lp:~gary/charms/oneiric/buildbot-slave/extra-packages (revno 23) |
| 2012/03/06 Benji York merge from trunk (revno 22) |
| 2012/03/06 Benji York - tweak the lpbuildbot example config to specify alternate key names - make the buildbot group creat (revno 21) |
| 2012/03/02 Francesco Banconi [r=gmb] upgrade-charm hook. (revno 20) |
| 2012/03/01 Benji York [r=gary] add a work-around to a bug in LXC (revno 19) |
| 2012/03/01 Benji York correct the buildbot home dir (revno 18) |
| 2012/03/01 Brad Crittenden [r=frankban] Install python-shell-toolbox in the install hook. Temporarily add copies of helpers.py (revno 17) |
| 2012/02/29 Francesco Banconi [r=gmb] Added revision file. Removed juju_wrapper. (revno 16) |
| 2012/02/28 Gary Poster [r=bac] move HACKING to README per review (revno 15) |
Lint Check
- err: Charms need a maintainer (See RFC2822) - Name <email>
- warn: missing recommended hook start
- warn: missing recommended hook stop