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

Don't download/fetch if the output folder is already up to date #41

Open
bweggersen opened this issue Sep 26, 2019 · 0 comments
Open

Don't download/fetch if the output folder is already up to date #41

bweggersen opened this issue Sep 26, 2019 · 0 comments

Comments

@bweggersen
Copy link
Member

bweggersen commented Sep 26, 2019

Currently, backfill will create a hash and then try to download the content belonging to that hash. In many cases, this is unnecessary as the local output folder might already be up to date. Is there a way to figure out whether the output folder is up to date and then skip fetching?

We could create a local mapping between the hash of the output-folder and the hash of the package. Then, on a later run, after we have created a hash of the package, we could create a hash of the output folder and then do a lookup to see if the output folder hash points to the package hash. In which case we don't have to even do a fetch.

This problem might be related to the clearOutputFolder config option. This value is false by default, which means the output folder doesn't get cleared between runs and between scripts that might be outputting to the same output folder in the same package (i.e. prepare and build). It is possible that hashing the output folder might not work well, as the output folder might change too often.

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

1 participant