@avsm I think the main reason we started using Jenkins was that IncludeOS was private at the time we started implementing a CI. Now that it is open source we have a lot more options.
If you could do a write up on your testing procedure that would be great, we are also planning on expanding our tests to include multiple OS versions.
Our current Jenkins procedure is as follows: new commit triggers a webhook -> spawn a new clean vm with ubuntu 14.04 -> download the pre compile libraries we need from the latest release on github -> download the newest committed version of IncludeOS -> build and run -> perform some basic networking tests to the VM.
We also do daily compilations from source instead of using the pre compiled libraries.