geerlingguy
commented
9 years ago One quick note: So far, Travis CI's new container-based test runners don't allow sudo access, so Travis may get a lot less useful for general infrastructure tooling test runs in the future. I'm hoping they will allow sudo in the containers at some point... but even there, it could make for some strange results.
The jury's out, but I would definitely be in favor of figuring out a simple/effective standard for test integrations—at a bare minimum, we can (with whatever Travis infrastructure exists) run Ansible syntax checks.
Travis provides CI integration, for free, for all public Github repositories.
We could encourage people to set up their roles to run against Travis, and alter the UI to privilege roles that are working in Travis. @geerlingguy did a nice write-up on this:
https://servercheck.in/blog/testing-ansible-roles-travis-ci-github
If we can then present a filter that shows only the Ansible roles that are "passing" in Travis, that's a great way of showing "quality" beyond ratings.