Skip to content
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

Merged
merged 7 commits into from
Jan 27, 2016
Merged

travis-ci config #17

merged 7 commits into from
Jan 27, 2016

Conversation

chipitsine
Copy link
Contributor

travis-ci allows automation of pull request build testing

@mattock
Copy link
Member

mattock commented Jan 27, 2016

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.

mattock added a commit that referenced this pull request Jan 27, 2016
@mattock mattock merged commit d8dff8d into OpenVPN:master Jan 27, 2016
@chipitsine
Copy link
Contributor Author

what is "build-complete" ?

@mattock
Copy link
Member

mattock commented Jan 29, 2016

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.

@chipitsine
Copy link
Contributor Author

if you mean creating nsis installer on travis, I think it would be overkill and not very neccessary.
currently, I think, travis will build pull request and tell us whether build is passing or not. let us stick on that thing first.

@mattock
Copy link
Member

mattock commented Jan 29, 2016

Yes, exactly. We're on the same page then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants