Closed josephhardinee closed 6 years ago
Thanks, @josephhardinee ! Merged. I think since I am just an admin, that @pfhein will have to actually get Travis CI working on the repo, yes?
I think you can, but I may be wrong. If you log into travis CI with your github account, it should give you a list of options for which repositories you can activate it for.
This adds travis CI integration support to CSU_RadarTools. I added two tests and set up pytest as the test runner. The tests just verify that the package can be installed. I set up a build matrix to try out python 2.7, 3.4, 3.5, and 3.6, using both cython and f2py. I had to add a search for an environment variable to setup.py to allow both of these to be tested easily (It still defaults to CYTHON if no environment variable is set).
This also has my other previous pull request included as I needed that to get the tests running satisfactorily. You may want to merge it first. You'll want to eventually add more unit tests, this is just meant as a skeleton to do the CI for you. You'll need to log into travis CI and enable this for your repo if you want it to be run (After merge). Also
I would make sure to squash my commits on merge. The commit messages are mostly useless as I was just needing to trigger new builds.
Let me know if you have any questions.