Adding a continuous integration (CI) tool would allow the test to be run before the pull requests are merged into the master branch. By testing the code before it is merged it would prevent people from breaking the build.
The upstream master has been broken on this project in the past, and it had an adverse effect on the productivity of some of the contributors working on the project. Therefore, the addition of a CI tool would increase productivity. Travis CI may be a good choice. Travis CI can be integrated with GitHub and is free for open source projects (source: https://github.com/marketplace/travis-ci).
@softeng-701 The integration of a CI tool looks to be quiet straightforward and would involve a bit of research as well as the creation of a build script which would run the unit tests. I think this issue should be labelled small.
Adding a continuous integration (CI) tool would allow the test to be run before the pull requests are merged into the master branch. By testing the code before it is merged it would prevent people from breaking the build.
The upstream master has been broken on this project in the past, and it had an adverse effect on the productivity of some of the contributors working on the project. Therefore, the addition of a CI tool would increase productivity. Travis CI may be a good choice. Travis CI can be integrated with GitHub and is free for open source projects (source: https://github.com/marketplace/travis-ci).
@softeng-701 The integration of a CI tool looks to be quiet straightforward and would involve a bit of research as well as the creation of a build script which would run the unit tests. I think this issue should be labelled small.