Add travis

[kdaily]

to run tests

[kdaily]

This is blocked by https://sagebionetworks.jira.com/browse/SYNPY-639

[sgosline]

Once the jira is fixed this looks good to me.

[philerooski]

I've been using pytest to run my unit tests. Are there going to be any compatibility issues?

[kdaily]

Short answer: yes.

[kdaily]

We should use pytest anyways, nose hasn't been maintained.

[kdaily]

@sgosline see #51

[kdaily]

@philerooski @teslajoy any idea why this would be failing getting the version number from github (but only when running on Travis)?

https://travis-ci.org/Sage-Bionetworks/annotator/jobs/348357181

[teslajoy]

Not sure, but a couple of brainstorming-thoughts on the travis env:

I'd probably try to remove pip install -r ... and leave pip install . (maybe some library dependency stack is being corrupted)
I'd also try to get a pip install . --verbose to see a bit more of the traceback
If non of this worked, I'd try to change the env.

[kdaily]

need the pip install -r requirements.txt because setup.py has requirements (including requests which is causing the error).

[kdaily]

Ran it a few more times, finally figured it out:

{u'documentation_url': u'https://developer.github.com/v3/#rate-limiting', u'message': u"API rate limit exceeded for 52.3.55.28. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"}

We need to use a Github API Token in our request in order to guarantee this call will work.

[kdaily]

Looking further, we might not be able to do it this way because to supply the Github auth token as an environment variable (standard way) won't work on Travis for PR builds:

https://docs.travis-ci.com/user/pull-requests#Pull-Requests-and-Security-Restrictions

[teslajoy]

I added TSD_GITHUB_TOKEN to travis via:
https://www.tomsdev.com/blog/2015/tsd-travis-ci-github-rate-limit-reached/

would have to add it to global env and in code if it exists add to auth of requests.get() else just leave request as is for local users env.
http://docs.python-requests.org/en/master/user/authentication/
https://docs.travis-ci.com/user/environment-variables/

[kdaily]

After contemplating what this code is doing, not sure it's the best way to get the version!

This PR is a good example - when I install, I'm going to report that my version is whatever is the latest version in Github - but that isn't true! This code is newer than the most recent version. We need to manage the state of versions locally (in this codebase) or through git (not Github) tags, not based on previous releases.

In order to get this in, I'm going to make another issue/PR to remove and change the versioning process first.

[kdaily]

Blocked by #88.

[teslajoy]

Agreed! Great idea as always!