Travis #32
Merged
Travis #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Here's an example of a pull-request with an active travis hook: travis-ci-examples/php-example#8 |
|
ACK. Can you update the build instructions too, to include autogen.sh? |
This adds a huge matrix of builds. The undesirable ones can be removed.
|
updated README |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #29. Travis provides excellent integration with github. It will chime-in as necessary for pull-requests.
I've been working on pull-req stuff for bitcoin core, and figured this would be a good test-case to see how viable Travis is.
See an example build-matrix here. https://travis-ci.org/theuni/secp256k1/builds/27738000
To take the pull-req features for a test-run before pulling, you can submit a pull req to my travis branch here: https://github.com/theuni/secp256k1
To setup: head to https://travis-ci.org and give it the necessary api access to your repo. After that, any branch that contains a .travis.yml file will be built for each push/pull-req.