ratzpo and diego and pcrews before we go and use another CI system again, I would recommand Diego that you discuss with Patrick to try to reuse what we are implementing on Jenkins. Patrick promised me to compare various online CI including Travis. The reason is that we cannot afford to spread the CI systems (buildbot, jenkins, travis, ...) for a so small company & engineering team.

In addition to Julien's comment, I'd like to point out that there is/used to be a buildbot for JDBC builds, so "test for every commit and pull request" is there.
It makes imo more sense to clean up existing unit tests, new additions (pool etc) are far away from what is called unit testing (they are smoke tests, integration test and take so much time, that running junit is not fun anymore)

Travis is indeed promising, but I do not think it offers anything that Jenkins does not.
It is mainly a trade-off between managing infrastructure systems or not - Travis allows for some 'magic' that doesn't require administration, but I also feel that this convenience could ultimately paint us into a corner. That is, it does some compelling things that solve short term problems, but it comes with larger limitations that emerge later.

While Jenkins can provide the capabilities listed as requirements for connectors, I do not think Travis can satisfy the demands of the Enterprise team, particularly in terms of supported platforms
http://docs.travis-ci.com/user/installing-dependencies/#Installing-Ubuntu-packages
Installing Ubuntu packages # Our Linux environment is currently based on Ubuntu 12.04 LTS.

We have to test many platforms, including POWER8 machines - Jenkins allows one to plug in different slaves to provide for any necessary build environment.

There are a number of ways to tie Jenkins and git repos together to provide testing and gating (kick off tests on each push, auto-merge changesets that do pass tests, etc), it is largely a matter of defining needs and setting things up appropriately.

I agree that travis is only a starting point. You can integrate several layers of CI with github: see https://github.com/puppet-community/puppet-corosync/pull/142 which is tested against pcci and travis. And if you go for Jenkins, take a look at what openstack does: https://github.com/openstack-infra/jenkins-job-builder

At least now we have a public set of tests, and it did not take long to get that running.

Actually, all the tests are working with only one instance of DB.
Next version - that will handle replication, galera and other things - has to be tested with multiple instance of DB.

Travis has the avantage of being simple, and to permit every contributor to check that CI is working easily.
The problem is that travis mount only one docker image. That's good, but will not permit testing against multiple DB instance or those server must be external to docker, and so public with account defined in script. That doesn't sound good.

So the best may be a compromise : use the two of them :

• keep the travis script to permit testing mono-server tests.
• use jenkins internally to do the same + multi-server (galera, replication ...)

You can have travis and jenkins at the same time connected to the git repo, there is no need to hide this internally.

https://github.com/travis-ci/travis-build/pull/303 will help when they finish it off.

http://next.travis-ci.com/ has ubuntu 14.04