Webservice / UI for reproducibility validation

[choldgraf]

We should have some way to "validate" a repository for reproducibility / reliability / etc.

[choldgraf]

I think this is an issue for repo2docker as opposed to BinderHub. Closing this to talk here: jupyterhub/repo2docker#93

[yuvipanda]

IMO this is an issue for binderhub, since it'll be the webservice that'll need to run repo2docker and provide UI for a 'can reproduce' / 'can not reproduce' result. It probably relates to multiple repo2docker issues that can be opened once we figure out what this should be like.

…

On Tue, Nov 28, 2017 at 6:02 PM, Chris Holdgraf ***@***.***> wrote: I think this is an issue for repo2docker as opposed to BinderHub. Closing this and opening something up there — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#102 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB23jHYmL3Ej4KXkiW5cAt1BRuKSWmZks5s7Ls7gaJpZM4PQFRm> .

-- Yuvi Panda T http://yuvi.in/blog

[willingc]

@choldgraf Perhaps open a new issue here re: @yuvipanda's suggestion re: Create webservice and UI for reproducibility validation.

[choldgraf]

OK cool - I'll reopen this and rename the top-level comment

[betatim]

Do you actually need to build the image to check reproducibility? I was expecting that we'd parse the various build pack files and decide based on what we find. For a requirements.txt you'd get a tick if all your packages are versioned, etc. More like a linter than trying to compile&execute.