Continuous integration!

[aboodman]

We need some. Probably in connection with #67 .

[aboodman]

@arv recommends https://travis-ci.org/.

[arv]

I created a simple public repo to try out go+travis

https://travis-ci.org/arv/arv-test-go-travis-ci/builds

[aboodman]

Travis is significantly less :( than I am used to CI being. Too bad it doesn't support benchmarks.

[aboodman]

OK, we are converging on a plan:

• We think that we can't easily use a hosted thing for benchmarking because we will be on a shared machine, so it will be too noisy.
• We can have a dedicated machine hosted, but another way to do it would be to just have an old machine in the attic that is running the perf tests.
• Raf has offered to dedicate a machine to the cause.
• We can have a little scheduled job on the perf machine that periodically pulls from github and runs a test. Then it can commit to an s3 noms instance the hash it tested and the number it got.
• Then we can display that data ... somewhere. Ideas include:
  • Integration with slack? (/me handwaves)
  • Adding a test to whatever continuous testing we have that checks the latest number. This wouldn't tell you which test broke the perf, but it would tell you it broke recently.

Assigning to raf to bring computer.

[aboodman]

yeah.