The document discusses the importance of continuous integration (CI) in software development, highlighting the benefits of using Travis CI as a tool for open-source projects. It addresses common challenges faced when sharing source code and emphasizes the automation of testing and deployment processes. Additionally, it outlines configurations for various programming languages and presents resources for further learning about CI practices.

1. JJ
SHOW AN OPEN SOURCE PROJECT SOME LOVE
AND START USING TRAVIS-CI
Joel Byler
@joelbyler
January 10, 2014
CodeMash 2.0.1.4
Kalihari Resort
Sandusky, OH
Sunday, January 12, 14

2. WHO AM I?
JOEL BYLER
 Aspiring Software Craftsman
 Organizer for Cleveland Ruby
Brigade (aka CleRb)
 Enterprise Java developer
 Actively growing my Ruby and
JavaScript skills
Sunday, January 12, 14

3. WHO ARE YOU?
 Want to get involved in an Open
Source Project?
 Currently maintaining an Open
Source Project and interested in
your CI options?
Sunday, January 12, 14

4. COMMON PROBLEMS WHEN
SHARING SOURCE CODE
 Work’s on my machine syndrome
 Didn’t realize I need to test on that
version of ruby/node/etc.
 Pull requests - how do I know if
this will break the build?
 Would love run tests on commit,
but don’t have $$$ for equipment.
Sunday, January 12, 14

5. CONTINUOUS INTEGRATION
...is the practice, in software engineering, of merging all
developer working copies with a shared mainline several
times a day.
~Wikipedia
...is a software development practice where members of a
team integrate their work frequently
~Martin Fowler
Sunday, January 12, 14

6. CONTINUOUS INTEGRATION CONTD.
Once the code is built, all tests should run to confirm
that it behaves as the developers expect it to behave.
~Wikipedia
...verified by an automated build (including test) to detect
integration errors as quickly as possible...
~Martin Fowler
Sunday, January 12, 14

7. TRAVIS-CI
 Hosted
 Free for open-source projects
 Supports MANY Languages
 Can run against multiple
runtime versions
 MOAR!
Sunday, January 12, 14

8. You don’t have to take my word for it.
WHAT PEOPLE ARE SAYING
Sunday, January 12, 14

9. QUOTES
What Github did for sharing code, Travis CI will do for
testing code
- Brian Ford, Rubinius, @brixen
I'm sure there was life before @travisci, but I choose
to ignore it.
- Jeff Casimir, Jumpstart Lab/Hungry Academy @j3
I have used many CI systems, but Travis is the most
awesome one so far!!
- Aslak Hellesoy, THE Cucumber Guy, @aslak_hellesoy
Sunday, January 12, 14

10. TRAVIS BUILD LIFE-CYCLE
Any of the following steps will fail build when finishing
with a non-zero exit code
-clone github repository
-cd to new directory
-before_install:
prepare the system
-install:
install prerequisites or dependencies
-before_script:
prepare your build for testing
-script:
specific to project language
==== build will not fail past this step ====
-after_success:
-after_failure:
-after_script:
Sunday, January 12, 14

11. Test all the things!
LANGUAGES
Sunday, January 12, 14

12. WORKS FOR YOUR LANGUAGE
(PROBABLY)
C
JAVASCRIPT (WITH
C++
NODE.JS)
OBJECTIVE-C
PERL
PHP
PYTHON
RUBY
SCALA
CLOJURE
ERLANG
GO
GROOVY
HASKELL
JAVA
Sunday, January 12, 14

13. RUBY
.travis.yml
Super simple!
Sunday, January 12, 14

14. COMPLEX BUILD
Sunday, January 12, 14

15. JAVA
.travis.yml
Sunday, January 12, 14

16. JAVASCRIPT
travis.yml
Sunday, January 12, 14

17. THE BUILD IS PASSING!
badges for your website
Sunday, January 12, 14

18. DEMO
https://github.com/joelbyler/roman_numeral.js
 travis gem
 travis login & travis init
 notifications
 travis-lint gem for validation
Sunday, January 12, 14

19. DEMO
https://github.com/joelbyler/roman_numeral.js/blob/master/media/TravisCI.mov?raw=true
Sunday, January 12, 14

20. Sunday, January 12, 14

21. Sunday, January 12, 14

22. Know that merging a pull request won’t
break the build.
PULL REQUESTS
Sunday, January 12, 14

23. THE BUILD IS PASSING!
Sunday, January 12, 14

24. Why start trusting a human now?
AUTO DEPLOYMENT
Sunday, January 12, 14

25. CONTINUOUS DEPLOYMENT
In the same vein the practice of continuous delivery
further extends CI by making sure the software checked
in on the mainline is always in a state that can be
deployed to users and makes the actual deployment
process very rapid.
~Wikipedia
A natural consequence of this is that you should also
have scripts that allow you to deploy into production with
similar ease.
~Martin Fowler
Sunday, January 12, 14

26. DEPLOY YOUR CHANGES TO:
Heroku
Nodejitsu
Engine Yard
OpenShift
cloudControl
RubyGems
PyPI
NPM
Sunday, January 12, 14

27. A RUBY EXAMPLE, DEPLOY TO
RUBYGEMS.ORG
Sunday, January 12, 14

28. A NODE EXAMPLE, DEPLOY TO
NPMJS.ORG
Sunday, January 12, 14

29. ADVANCED FEATURES
 parallelized builds (unit vs int. tests)
 databases
 GUI & Headless browser testing
Sunday, January 12, 14

30. Not a sharer?
PRIVATE REPOSITORIES
Sunday, January 12, 14

31. PRICING
as of 1/9/2014
Sunday, January 12, 14

32. ALTERNATIVES
 drone.io (free for open source)
 werker.com (free beta)
 circleci.com
 cisimple.com
 tddium.com
Sunday, January 12, 14

33. RESOURCES
Travis-CI
https://travis-ci.org/
Travis-CI Blog
http://about.travis-ci.org/blog/
Travis-CI Source
https://github.com/travis-ci
Continuous Integration, by Martin Fowler
http://www.martinfowler.com/articles/continuousIntegration.html
Sunday, January 12, 14

34. RESOURCES CONTINUED
Code Coverage
https://coveralls.io/
Dependencies
https://gemnasium.com/
Version Badge
http://badge.fury.io/
Quality Analysis
https://codeclimate.com/
Sunday, January 12, 14

35. THAT’S A WRAP!
Joel Byler
@joelbyler
Sunday, January 12, 14

36. COME FLOAT WITH US!
Located on a 10,000 square foot boat on the
Cleveland waterfront, our team exemplifies
how Agile values & principles are practiced.
Come float, deliver, and learn with us, or
leverage our expertise to help you change
your company culture.
@leandog
leandog.com
GDI
Sunday, January 12, 14