Continuous integration

[bherr2]

Use Travis CI to automatically test, generate documentation, and build on commits.

• On commit to develop, run tests. If passed generate documentation and built ontology files + json tree export. Push generated data to staging branch.
• On commit to develop, run tests. If passed generate documentation and built ontology files + json tree export. Push generated data to gh-pages branch (ie published to github.io).
• On tag push, run tests. If passed generate documentation and built ontology files + json tree export. Push generated data to a GitHub release. This will be where official releases will go.

@bherr2 can help get the Travis CI setup, but the code pieces will need to come from @SamuelFriedman.

[bherr2]

One thing that will be required for this is to be able to run all the workflow from the command line. I think @SamuelFriedman python code should be able to be setup like that. For converting to different formats/reifications, Protege does not have a CLI.

On their forum, someone pointed out this project: http://robot.obolibrary.org/convert which can convert owl into different formats on the command line.

Are there other parts of the workflow that need CLI'd? Doc generation and testing come to mind, not sure what's out there yet.

[bherr2]

Hmm, actually that robot library does have some stuff we could use for testing including validation and verification.