Check out pull requests for Rails
and click on the little ✔s and ✗s.
Docker enables us to bring together lots of working parts, unusual languages, and heavy dependencies.
FROM ubuntu:trusty RUN apt-get update -q && \ apt-get install -y -q --no-install-recommends \ ca-certificates \ cowsay \ git \ make RUN ln -s /usr/games/cowsay /usr/bin CMD git clone https://github.com/matsen/p-neq-np.git && \ cd p-neq-np && \ make
git clone https://github.com/matsen/cowsay-build-env.git cd cowsay-build-env/ docker build -t $USER/cowsay-build-env . docker images docker run -t $USER/cowsay-build-env docker run -it $USER/cowsay-build-env /bin/bash
apt-getin your Dockerfile
Either push directly:
docker push $USER/cowsay-build-env
Or set up an automated build as I have for this project:
In fact, I wrote a little shim that would post to our Slack channel with the results of an automated build.
But, there are tools that make the process smoother and more logical, such as Wercker.
Specify the Docker image used for the build:
Specify what the build should do:
build: steps: - script: name: build code: make
When pushed to Wercker, you get a build page like this.
build: after-steps: - slack-notifier: url: $SLACK_URL channel: microbiome username: pplacer build
Upload docs to Github pages:
deploy: steps: - ematsen/gh-pages: token: $GITHUB_TOKEN repo: matsen/pplacer path: docs/_build/html
* and a little fussy to debug. Use yamllint.com.