This repository has been archived by the owner on Feb 11, 2023. It is now read-only.
Travis CI support #2
Merged
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
craigbruce
added a commit
that referenced
this pull request
Jan 10, 2013
Travis CI support - This was on my todo list, cheers!
|
Just a note that there appears to be issues with the Travis build. The build status is showing up as unknown and the page on the site doesn't seem to load. |
|
my mistake didn't make a travis-ci account. sorted now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This allows for tests to run automatically on every push via Travis CI. Depends on #1.
If you haven't used Travis CI, a brief explanation follows.
Once merged into the main repository, you would have to create an account on the Travis CI website. After doing that and turning on builds for this repo, they will be run automatically on every push. You can also configure tests to run for every pull request.
You can also add a nice build status indicator with the following Markdown: