Travis – a distributed build system
Travis is an attemp to create an open-source, distributed build system for the Ruby community that
1. allows open-source projects to register their repository and have their test-suites run on demand
2. allows users to contribute build capacities by connecting a VM that runs a build agent somewhere on their underused servers
If you are interested in Travis please subscribe to the Google group and check out my introductional blog post over here: Travis – a distributed build server tool for the Ruby community
Travis consists of four main parts:
- A Backbone.js single-page application that runs client side.
- A Rails 3 application that serves to the in-browser application and takes pings from Github.
- A Resque worker for running a project’s test suite remotely.
- A websocket server for tailing build results to the browser. (This server is currently started within the Rails app process.)
To get an idea: 1:20 quick demo screencast
- Get a working application up and running that can distribute build requests to manually installed build workers and report back to browsers. Most simplistic UI that ever would make sense for this. Have a restricted set of allowed Github repositories.
- Allow people to login through Github OAuth and somehow maintain a list of repositories they’re interested in.
- Create VM images so that people can easily install and start build workers on underused or contributed servers.
This code is a spike and everything will change very likely. It is here to try out a few basic concepts and building blocks and ask people to share their opinion.
Nonetheless we currently have a working demo application running on http://travis.heroku.com which uses
- RedisToGo as a Redis store
- Pusher as a Websocket server
- A virtual server granted by Avarteq for running a Resque worker.
Each of these components could be replaced with something else, e.g. one could easily use a different Redis server.
Currently one can sign in via Github OAuth2 and an account will automatically be created.
In order to register a project for builds on Travis just supply a Github service hook for the following URL:
You can get a Travis token on the Travis profile page by signing in to your application via Github OAuth2.
One can check in a file
.travis.yml in order to specify a custom build script (by default
rake will be executed). See this file as an example.
Please note that this is an experimental installation.
To install your own instance of Travis you need to supply various configuration settings:
$ cp config/travis.example.yml config/travis.yml
In order to push these settings to Heroku you can use:
$ rake heroku:config
Starting a local worker:
$ RAILS_ENV=production VERBOSE=true QUEUE=builds rake resque:work
Or using God:
$ cp config/resque.god.example config/resque.god $ god -c config/resque.god
Running the tests
Integration tests are implemented using Jasmine and can be run in the browser:
$ RAILS_ENV=jasmine rake db:migrate db:fixtures:load $ rails s thin -e jasmine $ open http://localhost:3000
To run the unit tests simply do:
$ ruby -Ilib -Itest test/all.rb
My first spike was using Nanite for running workers. These materials are now outdated but might be interesting: