1st take on continuous integration via travis #15
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
rhiever
pushed a commit
that referenced
this pull request
Nov 16, 2015
1st take on continuous integration via travis
|
Let's give this a go. I just set it up and made a push. Does it automatically update the README with the build status? |
|
Should be all fixed now, needed to create a new pull request, see #19 for details!
Yes! :) |
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.
Let's see if this does the job ... I guess there will be some weird stuff to debug in the beginning, but let's see what Travis-CI reports back so that we can debug more efficiently.
So, you'd need to login at https://travis-ci.org via your GitHub account and enable travis for this repo. I can't remember exactly, but there should be an option for testing other branches except master. I'd enable this, make a small change to the repo (best in a new branch that you can delete later) to trigger the first build.