Skip to content
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

Merged
merged 12 commits into from
Mar 18, 2020
Merged

Add an intial travis.yml #728

merged 12 commits into from
Mar 18, 2020

Conversation

shankari
Copy link
Contributor

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:

Option Cost Limitations non-docker support docker/compose support
CirrusCI Free number of concurrent runs per user Unix or Windows VMs, but is not part of the regular examples all examples
CircleCI certain number of credits for linux and OSX. Unsure about windows - inconsistent info docs say that it supports VMs, not a lot of docs though docker has good support, and so does docker-compose
TravisCI Free Can't see any Yes (new VM for every run) docker and docker-compose support

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:

We are implementing these changes with GitHub Apps, which provides a tighter integration with GitHub and finer control over repository and subscription ownership and permissions.

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.

Travis.com (new) Travis.org (obsolete)
Screen Shot 2020-03-12 at 9 30 51 PM Screen Shot 2020-03-12 at 9 37 44 PM

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1165/
Test FAILed.

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1166/
Test FAILed.

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1167/
Test FAILed.

To ensure that we don't run in a virtualenv
@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1168/
Test FAILed.

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1169/
Test FAILed.

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1170/
Test FAILed.

+ remove python and apt-update to reduce space used
@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1171/
Test FAILed.

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1172/
Test FAILed.

…into enable_ci

Pull in the conda environment fixes
@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1177/
Test FAILed.

And source activate elsewhere
@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1178/
Test FAILed.

@shankari
Copy link
Contributor Author

Screen Shot 2020-03-17 at 9 25 26 PM

@shankari shankari merged commit fb90217 into e-mission:master Mar 18, 2020
@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/e-mission-server-prb/1179/
Test FAILed.

@shankari shankari deleted the enable_ci branch April 17, 2020 00:34
jf87 pushed a commit to jf87/e-mission-server that referenced this pull request Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants