Deconstructing Travis
Presenter: Josh Kalderimis
Josh is a top 30 Ruby on Rails contributor and has been working with the framework since 2008. He maintains a bunch of open-source Ruby projects, including multi_json, linkedin, faraday_middleware and his own completeness-fu. He's also one of Amsterdam.rb's organizers, and an integral part of the core Travis-CI team.
Unless you have been living under a rock for the past year you might know of Travis CI, the continuous integration service for the open source community.
Travis started as a single GitHub project which was a rails app and a resque background task. Compare that to 12 months later where Travis is now four separate deployable apps, uses two different rubies (1.9.2 and jruby), and comprises a total of 10 GitHub projects.
Apart from looking at how Travis works now, we will also look at how it got there, and how we broke Travis up into smaller more manageable, more concise encapsulated services.
- This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
- If you're interested in the generator code, see the "generator" directory.
- This layout is just a suggestion.
- Bullet points might work well. Paragraphs too. Up to you. :)
