Continuous Integration

A development practice of integrating code into a single build multiple times per day.

Builds are usually automated and depend on thorough automatic tests to ensure they complete properly and without issue.

We are not cavemen

Enter Travis CI

Let's Review!

1. Enable our repository on travis-ci.com
2. Create a .travis.yml file that lists the steps of our build process
   • Specify project language
   • Configure dependencies, databases, etc.
   • Execute post-build steps (such as tests)
3. Push our .travis.yml to our GitHub repo
4. Bask in the glory of continuous integration

Futher Reading

• Hosted CI servers: https://travis-ci.org, https://drone.io/
• Advanced topics: Deployment, Environment Variables, Headless Browser Testing (with PhantomJS)
• https://github.com/Lancey6/aaa_fullstack_1511_travis
• http://blogs.collab.net/devopsci/ten-best-practices-for-continuous-integration
• http://www.continuousintegrationtools.com/
• These slides: http://slides.com/dreeve/deck/