Get continuous integration tool(s) properly configured

[spencerahill]

I'm pretty sure that the Travis-CI tool is improperly configured to the point of being meaningless. It certainly doesn't run our test suite -- otherwise it would report the failures related to #50.

This is likely straightforward enough to fix.

[spencerahill]

One potentially difficult task will be to get the tests to somehow run on the GFDL analysis machine within the continuous integration framework. It's great if the CI tools run the tests in some environment such that the GFDL-file-specific tests are skipped (c.f. #42), but it would be even better if we somehow configured it such that the tests are run on the analysis cluster.

It's possible this is easy to do, I just haven't looked into this yet.

[spencerahill]

Continuum has some instructions on how to do the Travis CI step using conda: http://conda.pydata.org/docs/travis.html

This requires that we host the package on an Anaconda channel. Info here: https://docs.continuum.io/anaconda-cloud/using#using-conda-packages

I couldn't immediately get the conda build to work on my local machine, a necessary pre-step to uploading to anaconda.org. So need to sort that out. Docs http://conda.pydata.org/docs/building/recipe.html and http://conda.pydata.org/docs/build_tutorials.html

[spencerahill]

Closed by #101 and #105