-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HELP NEEDED: Build infrastructure #106
Comments
Hello, I think I may have a solution. GitLab has great CI integration, and I'm thinking of setting up a privately hosted machine, or possibly asking my work (Stellenbosch University) to host open source code. Would you be interested in having someone run something like that? |
travis-ci can do testing and coverage. I think it can do release builds as well |
Today I had time to devote to this, and Travis is now running the tests against our PRs. While I haven't yet found a way to do test coverage stats, simply knowing if the PR breaks the tests is huge. @ajcollett - I want to thank you for your offer. There may be other projects with more strenuous testing requirements that would benefit more your proposed solution. In ofxparse's case, running a complete server just for a PR every few weeks seems like overkill. @nathangrigg - Thanks for setting up .travis.yml. You made my day when everything Just Worked. :) |
Ofxparse could benefit from having some infrastructure to do things like run tests and create releases. This issue is for discussing what tools are available and the merits of each. My own knowledge is not up to date..
Pretty much needed features:
Some nice to haves, but not critical:
What kind of solutions appear to be viable?
The text was updated successfully, but these errors were encountered: