Rafe Colton

Unless maybe `-f`/`--force` is supplied

Given a file tree `dockerfiles/Dockerfile`, the following scenarios will not build: * putting `Bobfile` in `dockerfiles/` dir * putting `Bobfile` at the top level * setting `Dockerfile:` value in yaml...

Add a parameter `--skip` to the `build` command to skip the build of certain containers. Alternatively, or in addition, hash the `Dockerfile` specified for that build step, store the info...

probably with `&r=1` - will make it more practical for human consumption (won't have to scroll to the bottom after each page refresh)

For example, if we're already pushing an image tagged with `:master`, a subsequent attempt to push the same one will fail, but in reality that build may contain a different...

When two docker-builder builds are run in succession without any changes to any of the source files, the build should be entirely cacheable. However running an `ADD . /path/in/container` still...

so we don't do any of the fancy copy/included/excluded stuff and just build the dang image

There are a couple places where the app code had to know about testing to prevent bad things from happening. This was also done to avoid putting the tests in...