Paddin my ignorance, what would we gain by having Travis CI build this repository? We already have three Jenkins build bots.

Paddin = pardon, silly phone :)

I'm 👍 with having this as part of the Jenkins' pipeline.

I initially went for Travis CI (proposed in #920, added in #987) because, contrary to the other tests, lint checks should not depend on the underlying OS version and we thus don't need to start a VM; a Travis container is faster. I also really appreciate the integration with GitHub. In particular, the configuration is part of the source code, which doesn't seem to be the case for the current Jenkins build bots.

/cc @drzaeus77 I have good experience with TravisCI, just a bit worried about the duplication. If it's only going to be used as a linter, I think it doesn't hurt -- it does provide very fast build feedback unlike the current build bots, and requires no additional maintenance on our part.

LGTM. Merge ready? cc @drzaeus77

Without Travis-CI (or some other CI) enabled, we'll probably have to do this again in a few weeks...