-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
dvc: introduce local stage cache #3603
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
efiop
force-pushed
the
1234
branch
3 times, most recently
from
April 7, 2020 05:19
e7d8355
to
97e8f00
Compare
efiop
changed the title
[WIP] dvc: introduce local build cache
[WIP] dvc: introduce local stage cache
Apr 7, 2020
efiop
commented
Apr 7, 2020
efiop
commented
Apr 7, 2020
efiop
commented
Apr 7, 2020
efiop
commented
Apr 7, 2020
efiop
commented
Apr 7, 2020
efiop
commented
Apr 7, 2020
efiop
force-pushed
the
1234
branch
2 times, most recently
from
April 7, 2020 13:41
df02586
to
116f1be
Compare
skshetry
reviewed
Apr 9, 2020
skshetry
reviewed
Apr 9, 2020
skshetry
reviewed
Apr 9, 2020
skshetry
reviewed
Apr 9, 2020
efiop
force-pushed
the
1234
branch
2 times, most recently
from
April 22, 2020 15:24
09937aa
to
85dfc7c
Compare
efiop
force-pushed
the
1234
branch
2 times, most recently
from
April 24, 2020 00:08
3813464
to
59b1911
Compare
efiop
force-pushed
the
1234
branch
4 times, most recently
from
April 29, 2020 17:25
c93f2cc
to
b5927f8
Compare
efiop
force-pushed
the
1234
branch
2 times, most recently
from
April 29, 2020 18:21
8554209
to
890e969
Compare
This patch introduces `.dvc/cache/stages` that is used to store previous runs and their results, which could then be reused later when we stumble upon the same command with the same deps and outs. Format of build cache entries is single-line json, which is readable by humans and might also be used for lock files discussed in iterative#1871. Related to iterative#1871 Local part of iterative#1234
efiop
changed the title
[WIP] dvc: introduce local stage cache
dvc: introduce local stage cache
Apr 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch introduces
.dvc/cache/stages
that is used to store previousruns and their results, which could then be reused later when we stumble
upon the same command with the same deps and outs.
Format of build cache entries is single-line json, which is readable by
humans and might also be used for lock files discussed in #1871.
Related to #1871
Local part of #1234
❗ I have followed the Contributing to DVC checklist.
📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here. If the CLI API is changed, I have updated tab completion scripts.
❌ I will check DeepSource, CodeClimate, and other sanity checks below. (We consider them recommendatory and don't expect everything to be addressed. Please fix things that actually improve code or fix bugs.)
Thank you for the contribution - we'll try to review it as soon as possible. 🙏