Open
Conversation
Contributor
|
To be honest, I wish travis didn't require code to be in the repo to work, in general I feel like the code will outlive the travis ci company. |
Author
|
Yep. On the other hand, it works as documentation how to run tests as well. I wish the format was not travis dependent. |
This file contains hidden or 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
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.
I've wrote a simple .travis.yml file for testing compiler on Travis CI: https://travis-ci.org/
Build status is green for my fork: https://travis-ci.org/shalupov/8cc/branches
Enabling this will automatically run tests for every commit and also for every pull request.
For enabling travis for your project you just need to log in with GitHub account on https://travis-ci.org and enable it for the repository.