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

repo2docker: 2021.01.0-7.gac41c20...2021.01.0-11.g1140dd1 #1797

Merged
merged 2 commits into from
Jan 26, 2021
Merged

repo2docker: 2021.01.0-7.gac41c20...2021.01.0-11.g1140dd1 #1797

merged 2 commits into from
Jan 26, 2021

Conversation

henchbot
Copy link
Contributor

@henchbot henchbot commented Jan 26, 2021

This is a repo2docker version bump. See the link below for a diff of new changes:

jupyterhub/repo2docker@ac41c20...1140dd1

Associated PRs:

  • Add a contentprovider for Software Heritage persistent ID (SWHID) #988

@henchbot henchbot changed the title repo2docker: 2021.01.0-7.gac41c20...0.11.0-195.g2f1914d repo2docker: 2021.01.0-7.gac41c20...2021.01.0-11.g1140dd1 Jan 26, 2021
@betatim
Copy link
Member

betatim commented Jan 26, 2021

I think we need to think for a moment before deploying this. I'm worried that we might have changed the name of the docker image we create. If this is true it will be as if we emptied our image cache -> lots of build traffic -> something to do in a quiet moment not during peak traffic (EU afternoon).

@manics
Copy link
Member

manics commented Jan 26, 2021

If I understand jupyterhub/repo2docker@983607f correctly the image name will only change if picked_content_provider.content_id contains chars that need to be escaped.

Looking at the (presumably most popular) git provider I don't think this is a problem since it's just the SHA
https://github.com/jupyterhub/repo2docker/blob/805c555173c3e2a2a3d02ad3a7c94480ac7dd968/repo2docker/contentproviders/git.py#L81-L85

@betatim
Copy link
Member

betatim commented Jan 26, 2021

True. So lets merge then?

@betatim betatim merged commit d7e6b84 into jupyterhub:master Jan 26, 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.

3 participants