-
Notifications
You must be signed in to change notification settings - Fork 10
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
Travis setup #13
Comments
@betatim Okay, so if I understand the point of this project correctly, the idea is a CD with If so, then I can start to check out what has been done and start migrating the CircleCI to Travis later this week. To be clear, my |
The primary goal of this example repository is to show how you can setup CI to test that you can still build a useful container image from your repository. Use case: you binderize your repository, then make lots of changes, now your repository doesn't build any more. Or the way you specified dependencies isn't good enough so with some update somewhere it stops working, etc Pushing the built image to (docker)hub is a cool feature that we get for free. So the thing to do here is to setup a travis build that uses |
FWIW, I've have a working CD setup using travis, repo2docker, and pushing to dockerhub here: https://github.com/pangeo-data/pangeo-stacks |
Nice! Do you want to add a link to it or (even better) add a |
@matthewfeickert made https://github.com/matthewfeickert/R-in-Jupyter-with-Binder which uses travis. It would be nice to work out how much of it we can take over here to replicate what is happening on circle CI but use travis instead.
The text was updated successfully, but these errors were encountered: