Configure continuous integration and continuous delivery with Travis CI

[dsummersl]

There is already a configuration file for Travis - it needs to be configured for this github project.

[specious]

With #70 merged, what's our forward strategy?

I'm thinking...

Continuous integration (code linting, unit and integration tests on a pre-configured system)

• Enable Travis CI for this repository
• Get right with rubocop (Appease the rubocop static code analyzer #71)
• Assess what we've got in terms of test coverage and discuss where we'd like to go with that
  • We have a test directory; I propose to review and document what we've got and how relevant it is with respect to the latest code base; pertinent discussions might be - Fix the test cases #24, update the test assertions so that they reference Durham, not San Fra… #57
  • rake test currently outputs an RSpec code coverage report stating 97.71% covered and 0 failures, 0 errors, 0 skips; what does this really mean?

Continuous delivery (delivery pipeline resulting in the ability to push tested code to production at any time)

• Configure automatic deployment to our staging environment upon successful completion of automated checks

This excellent screencast by @jamesward shows how to set up a continuous delivery pipeline with automatic deployment to a Heroku cloud server.

And this article by @robvanderleek gives a great step by step introduction to building a CI/CD pipeline.