Sunday 2nd June 2013 9.10pm

Sun, Jun 2, 2013

In preparation for Paul to start work next week on his GSoC project of porting my code to Boost, I've been fixing up my code with Continuous Integration (for every change you commit a bot runs a full set of unit tests to ensure everything works) using the free-for-open source Travis CI.

I have to say, I have been impressed with Travis CI: despite its clunky UI and less than great reporting, it's far more powerful than the CI we use in BlackBerry. Have a look at https://travis-ci.org/ned14/TripleGit at the final test, the one which always fails: this test specially installs GCC 4.8 and compiles the code with GCC 4.8 using Google's new compiler-based thread sanitiser v2 ported from clang before running a full set of unit tests looking for race conditions. That's very serious flexibility in testing config made possible only because Travis CI runs your tests inside a VM with a full dev environment plus root access, so you can actually do anything a shell script can do on a full fat development workstation with root perms. Nice, very nice.