GitXplorerGitXplorer
e

buildbot-docker-demo

public
4 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
35f2882b085330450d6ce9d5fa03e0df23ad719a

Automatically remove Docker latent build slaves, including volumes.

eewencp committed 10 years ago
Unverified
cd17f304595802d05816797844d63b6d76d22feb

Build via Dockerfile inside Docker slave.

eewencp committed 10 years ago
Unverified
c4608cb53c415773acfdf61eb28f22bebde58829

Add apt-cacher-ng support.

eewencp committed 10 years ago
Unverified
b4e4bf8cd05689f0aae70e3434bb5ffa5906966c

Add simplest config using Docker containers for builds.

eewencp committed 10 years ago
Unverified
5cac1c7506514e64dd6ea52201c69ce6311bea04

Initial commit.

eewencp committed 10 years ago

README

The README file for this repository.

Example configurations for using Docker with Buildbot.

This configuration adds apt-cacher-ng support so that your builds don't hammer package mirrors, even if you always run the build from scratch.

Assuming you've checked out this code to ~/buildbot-docker-demo, build the Docker images for the master, slaves, and apt-cacher-ng:

cd ~/buildbot-docker-demo/
pushd master; docker build -t buildbot-master .; popd
pushd slave; docker build -t buildbot-slave .; popd
pushd aptcacherng; docker build -t aptcacherng .; popd

Run the master as with the simple config:

docker run --rm --name bbmaster -p 8010:8010 \
    -v ~/buildbot-docker-demo/master/data/buildbot/master:/data/buildbot/master \
    -v /var/run/docker.sock:/var/run/docker.sock \
    buildbot-master

Then run the apt-cacher-ng container:

docker run --rm --name apt-cacher-ng aptcacherng

Since it has a name, we can link to it when creating slave containers. The only other change required is that we enable proxying through apt-cacher-ng on the slaves, a simple one line addition to the slave Dockerfile.