Travis CI to test Make #249
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
Closed
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.
Addresses #247. I followed a simple tutorial on my fork to set up Travis CI on a repository: https://docs.travis-ci.com/user/tutorial/. The owner of the repository has to set it up but it takes only a couple of minutes.
Then, I created a simple .travis.yml file and pushed it up to my repository. It successfully built on an Ubuntu instance. Now, whenever I push, it runs the commands under script.
For next steps, I think we could try to setup up qemu on the Ubuntu virtual machine used for testing probably by just adding another install under before_install. Then, we could start to setup some functional tests. Adding #154 would help testing most likely.
Here is a screen shot of it working:
