-
Notifications
You must be signed in to change notification settings - Fork 239
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
travis-ci config #17
travis-ci config #17
Conversation
This looks like a good starting point. Later we could go with build-complete, which would catch even more issues. Based on Travis-CI that should be doable. |
what is "build-complete" ? |
See the build documentation. That said, converting build-complete build process to Travis-CI would be way more difficult, because we'd need to install a bunch of dependencies, run custom scripts, etc. Plus my Windows "buidslave" already runs build-complete/build-snapshot against "master" and "release/2.3" branches on new commits, so I think we're fine. |
if you mean creating nsis installer on travis, I think it would be overkill and not very neccessary. |
Yes, exactly. We're on the same page then. |
travis-ci allows automation of pull request build testing