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

Travis setup #13

Open
betatim opened this issue Jul 23, 2018 · 4 comments
Open

Travis setup #13

betatim opened this issue Jul 23, 2018 · 4 comments

Comments

@betatim
Copy link
Member

betatim commented Jul 23, 2018

@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.

@matthewfeickert
Copy link

matthewfeickert commented Jul 24, 2018

@betatim Okay, so if I understand the point of this project correctly, the idea is a CD with repo2docker to deploy pushes to master as Docker images to Docker Hub. So in the same way that Binder allows users to run interactively on the web, this allows users to pull the same Docker image that Binder is using. Do I have that right?

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 .travis.yml probably won't be very helpful as it is just meant to provide enough CI to do tests. There is no CD component there.

@betatim
Copy link
Member Author

betatim commented Jul 29, 2018

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 repo2docker to build the container for the repository. Then we can extend it to push the image to a container registry. Another thing that would be good to illustrate (and is done in very basic terms in #8) is to not only build the container but try and execute something in. What to execute depends heavily on the contents of the repository, but we can show how to in general run things. This is useful because it tells you if there are missing dependencies or other misconfigurations.

@jhamman
Copy link

jhamman commented Jan 24, 2019

FWIW, I've have a working CD setup using travis, repo2docker, and pushing to dockerhub here: https://github.com/pangeo-data/pangeo-stacks

@betatim
Copy link
Member Author

betatim commented Jan 25, 2019

Nice! Do you want to add a link to it or (even better) add a .travis.yml to this repo based on your work there?

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

No branches or pull requests

3 participants