Closed yosoyjay closed 7 years ago
I've not used Travis or other CI systems before. Am I right in assuming the purpose of this is to notify someone (me? you? all contributors?) when code is pushed to a specific branch ($TRAVIS_BRANCH
- presumably configurable?) if any of the tests fail?
I'm happy to merge this, I just want to understand exactly what it's doing :)
FWIW I understand the whole docker side of things, it's only Travis which I'm not au fait with.
Yeah, so the idea is that tests are run automatically after a commit to catch bugs and regressions early on.
So this is what the changes include:
.travis.yml
) is configured it so that it reports whether all the Maven tests have passed.Right now I have it setup so that I get a notification from Travis after a commit providing an assessment of the tests. This required the following:
.travis.yml
file to the repoIf you setup a Travis account and accept the commit, then you'll get notification of test results for every commit including pull requests. So, it should eliminate some of the overhead of maintaining the project.
Great, thanks, useful to know.
Added a Dockerfile and .travis.yml file to facilitate continuous integration.