-
Notifications
You must be signed in to change notification settings - Fork 120
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
Add an intial travis.yml #728
Conversation
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
To ensure that we don't run in a virtualenv
Merged build finished. Test FAILed. |
Test FAILed. |
Maybe we are just running out of space...
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
+ remove python and apt-update to reduce space used
This reverts commit 9a1f295.
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
…into enable_ci Pull in the conda environment fixes
Merged build finished. Test FAILed. |
Test FAILed. |
And source activate elsewhere
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Add an intial travis.yml
As we can see from the history for #727, several of the jenkins builds are failing. And this seems to be due to jenkins issues - setting up conda fails sometimes, and connecting to mongodb fails sometimes. RISE supports suggests that I use a dockerized build instead.
But I also cannot rely on having access to the RISE build resources forever, specially as I transition out of UC Berkeley. Therefore, this might be good motivation to move to an external automated build/test system.
Some options that have been verified by GitHub, along with their evaluation matrix, are shown below:
Based on this, I think I will go with TravisCI for now. It has support for open source projects without any limitations, and it supports non-dockerized builds, which will help us transition the testing better. It also seems to have a better GitHook integration.
Tried to use TravisCI, but there seems to be an inconsistency in the documentation.
I found this guide on open source projects with Travis,
https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/#stq=&stp=0which said that:
However, when I try to actually sign up using travis-ci.com I get the following auth page, which gives travis the ability to write code to any of my repositories!! In travis-ci.org, I only had to give status write access, not code.