-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Support external local deps/outputs #764
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
Comments
As part of this enhancement, I'd caution against the step of moving the original to the cache (which is I think the usual and good behavior for internal deps/outs). My motivation for using external deps is the common case of multiple code repositories depending on the same dataset (with each repository being configured to have its own external cache). FYI, I had tried to simply symlink the external deps/outs into the repo ... which failed :)
Seeing the "Removing ..." step is what got me here. Thanks for adding this feature! |
Hi @itcarroll !
We actually never move dependencies to the cache, only when that dependency is also an output of some other stage. It has not been well tested yet, but starting from the upcoming 0.9.8 you would be able to use the same external cache dir for all of your projects so that you could avoid duplication.
Yeah, we do not support symlinks as deps right now, but that is a great idea! I've added #774 to our todo list. Thank you for the feedback! |
Fixes iterative#764 Signed-off-by: Ruslan Kuprieiev <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
We currently support external local cache, but deps/outs are not yet supported. Adding support for that should be pretty trivial, since a lot of infrastructure already exists for other types.
See https://discuss.dvc.org/t/shared-cache-directory/
The text was updated successfully, but these errors were encountered: