-
Notifications
You must be signed in to change notification settings - Fork 61
Investigate adding Continuous Integration #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have a branch that I am working on for this, but I need to break it out. I will submit a pull request for 1.2-wip soon. I'll update this issue when I have a stable version of my branch ready. As a sneak peak it uses phantom-js and runs our jasmine unit tests. |
Submitted pull request for this enhancement. I went with Travis CI, which nicely integrates with GitHub. The script loads our unit test pages in Phantom-js and runs all the tests to verify whether or not the build passed. view the pull request here: #58 |
Thanks Ali, nice work. |
Issue #43 - Travis CI integration
Mark, Can you create a Travis CI account for OpenF2/F2 and add the status image to the root readme then close this issue? Below are the quick steps to get that done, hopefully I didn't miss anything Go To https://travis-ci.org/ It will automatically pick up all branches that have .travis.yml in the root directory. You need to actually push the master branch to kick off the first build. After you have pushed and gone back to Travis CI to verify the build was successful you can grab the "build passing" image pretty easily... Go back to the travis-ci home page |
This went live today. |
https://travis-ci.org/ and https://circleci.com/ are possibilities.
I haven't used either of these, though.
The text was updated successfully, but these errors were encountered: