UPDATE: I now have a complete turnkey, all-in-one answer, see https://stackoverflow.com/a/49019950/300224. Only took 3 years to figure out!
According to the Travis documentation: https://github.com/travis-ci/travis-ci there is a concoction of projects that collude to deliver the Travis CI web service we know and love. The following subset of projects appears to allow local make test
functionality using the .travis.yml
in your project:
travis-build creates the build
script for each job. It takes the configuration from the .travis.yml
file and
creates a bash
script that is then run in the build environment by
travis-worker.
travis-cookbooks holds the Chef cookbooks that are used to provision the build environments.
travis-worker is responsible for running the build scripts in a clean environment. It streams the log output to travis-logs and pushes state updates (build starting/finishing) to travis-hub.
(The other subprojects are responsible for communicating with GitHub, their web interface, email, and their API.)