docker/hack
Daniel Mizyrycki f83c31e188 Packaging, issue #960: Document PUBLISH_PPA for staging/production release 2013-07-10 16:06:49 -07:00
..
dockerbuilder Packaging, issue #960: Document PUBLISH_PPA for staging/production release 2013-07-10 16:06:49 -07:00
environment development; issue #374: Update VM documentation 2013-05-01 15:59:54 -07:00
infrastructure Organize the project infrastructure: servers, dns, email etc. 2013-05-30 12:28:24 -07:00
PRINCIPLES.md More principles. Raw and unstructured to spawn discussion. 2013-06-11 09:27:36 -07:00
README.rst Testing|hack, issue #1009: Update make kack environment 2013-06-24 15:01:51 -07:00
RELEASE.md Documented release process for maintainers in hack/RELEASE.md 2013-06-29 22:08:25 -07:00
ROADMAP.md New roadmap item: advanced port redirections 2013-06-12 10:50:47 -07:00
Vagrantfile Testing|hack, issue #1009: Update make kack environment 2013-06-24 15:01:51 -07:00
allmaintainers.sh allmaintainers.sh: print a flat list of all maintainers of a directory (including sub-directories) 2013-05-28 20:55:07 -07:00
fmt-check.hook Contrib post-commit hook for checking gofmt 2013-04-11 11:30:35 -07:00
getmaintainer.sh getmaintainer.sh: parse MAINTAINERS file to determine who should review changes to a particular file or directory 2013-05-28 20:44:41 -07:00

README.rst

This directory contains material helpful for hacking on docker.

make hack
=========

Set up an Ubuntu 12.04 virtual machine for developers including kernel 3.8
go1.1 and buildbot. The environment is setup in a way that can be used through
the usual go workflow and/or the root Makefile. You can either edit on
your host, or inside the VM (using make ssh-dev) and run and test docker
inside the VM.

dependencies: vagrant, virtualbox packages and python package requests


Buildbot
~~~~~~~~

Buildbot is a continuous integration system designed to automate the
build/test cycle. 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.

When running 'make hack' at the docker root directory, it spawns a virtual
machine in the background running a buildbot instance and adds a git
post-commit hook that automatically run docker tests for you each time you
commit in your local docker repository.

You can check your buildbot instance at http://192.168.33.21:8010/waterfall