Closed johnrfrank closed 9 years ago
Doing CI for the code portions of OpenSextant (vice the data processing portions) makes sense, I'm just not familiar with Travis. Will check it out.
A docker container might be a really nice way of organizing this for both CI and general deployment. Have you looked at making a docker build file for this? We can maybe help get that started, if you're interested in it.
Docker looks interesting. Primary concern would be how it would merge with primary customer's integration and deploy environment.May start with straight Travis first.
First cut at Travis build working. Just code build, no real tests yet.
OpenSextant seems very cool and it has clearly had a lot of work put into it. It also looks like it isn't completely dormant/orphaned. It's too bad that the build and testing scripts are incomplete and bitrotting.
Has anyone looked at setting up Travis continuous integration (CI) for this?
http://docs.travis-ci.com/user/languages/java/
It seems like at least some of the build system bugs might be resulting from development on a Mac OSX case-insensitive file system, which makes the
ant
files vulnerable to case matching errors that are only detectable on a case-sensitive file system. That's the kind of simple thing that CI would help keep clean.