Travis CI is a distributed build platform that provides continuous integration services for open source projects.

1. T
Travis CI
A Distributed Build Platform for Open Source

2. Continuous Integration is a software
development practice where members
of a team integrate their work
frequently ... verified by an automated
build (including test) to detect
integration errors
- Martin Fowler

3. Travis CI is ...
• An Open Source
• Distributed
• Build System
• for the Open Source Community

4. Open Source ...
• Brain child of Sven Fuchs
• travis.heroku.com (December, 2010)
• Travis-CI (and subprojects) are open source
• github.com/travis-ci
• 20 members and growing
• Considered “Alpha” (but very functional)

5. Distributed ...
allows users to contribute build
capacities by connecting a VM that
runs a build agent somewhere on their
underused servers
• Travis-CI -- the web application runs on Heroku
• But Travis workers,VMs that run the builds, are
contributed by users

6. Build System ...

7. Build System ...
repo
git push

8. Build System ...
repo
travis
git push hook

9. Build System ...
repo
travis
git push hook
tasks

10. Build System ...
repo
travis
git push hook task
tasks

11. Build System ...
git clone
repo
travis
git push hook task
tasks

12. Build System ...
git clone
repo status
travis
git push hook task
tasks

13. Build System ...
git clone
repo status
travis
git push hook task
tasks

14. Build System ...
git clone
repo status
travis
git push hook task
tasks
updates

15. Open Source Community
• Travis CI is free to use for any public
GitHub project
• Travis is great for any Ruby project

16. But Can Also Build ...
clojure

17. Getting Started ...
1. Sign up with Travis CI using
your GitHub account
2. Enable the repositories that
you want Travis to build

19. git push

20. A Travis Worker Builds
Your Project...
$ rvm use 1.8.7
$ git clone git://github.com/YOUR/PROJECT.git
$ bundle install --path vendor/bundle
$ bundle exec rake

23. Announce Your Build
Status!
• Status Images
• E-mail Notifications
• IRC Notifications

24. E-mail Notification ...

25. Build Matrix ...
• Defined by your .travis.yml
• Configure ...
• Ruby versions (rvm)
• Custom Gemfiles
• Environment Variables
• Script to run

26. Jsonify .travis.yml
rvm:
- 1.9.3
- 1.9.2
- 1.8.7
- jruby
- rbx-2.0
env:
- RAILS_VERSION='~>3.0.0'
- RAILS_VERSION='>=3.1.0'

27. Jsonify .travis.yml
10
rvm:
- 1.9.3
- 1.9.2
Builds
- 1.8.7
- jruby
- rbx-2.0
env:
- RAILS_VERSION='~>3.0.0'
- RAILS_VERSION='>=3.1.0'

28. But Wait ...
There’s More!
• before / after scripts
• matrix exclusion
matrix: { exclusion: [{ rvm: 1.8.7, env:RG=1.3.6 }]}
• specify branches to build (white/blacklist)
# blacklist
branches:
except:
- legacy
- experimental

29. Built-in DB Support
SQLite3
MySQL
PostgreSQL
MongoDB
All Available with no extra setup required

30. What about ? ? ?

31. What about ? ? ?
Redis
sphinx memcached
CouchDB python
OpenJDK
ImageMagick
Selenium Riak

32. Vanity .travis.yml
rvm:
- 1.8.7
- 1.9.2
gemfile:
- Gemfile
env:
- DB=mongodb
- DB=redis
- DB=mysql
before_script:
- "mysql -e 'create database vanity_test;' >/dev/null"

34. The “Hosh” Factor

35. The “Hosh” Factor
What metrics do you use when evaluating
gems and applications?

36. The “Hosh” Factor
What metrics do you use when evaluating
gems and applications?
• GitHub watchers and forks
• RubyGems.org download count
• Recent commit activity
• Travis Build Status and History

37. In the works ...
• RabbitMQ replacing Resque
• SproutCore replacing Backbone.js
• Travis API
• Private Repos*
Sven’s Mantra
“Do the simplest thing possible then Improve”

38. Interesting Svenisms ...
• simple_states
• data_migrations
• hashr

39. Get Involved ...
1. put your apps on Travis
2. about.travis-ci.org
3. #travis on freenode

40. Is This Travis ?

41. Travis the Tractor

42. Travis Bickle