Skip to content

Log a warning and rebuild if needed when caching fails #2685

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

Merged
merged 2 commits into from
Aug 22, 2019

Conversation

priyawadhwa
Copy link
Contributor

We should never error out if caching fails. Instead, log a warning and rebuild the artifact if it still needs to be rebuilt.

Should fix #2677

cc @balopat @briandealwis @prary

@priyawadhwa priyawadhwa added the priority/p0 Highest priority. We are actively looking at delivering it. label Aug 19, 2019
@codecov
Copy link

codecov bot commented Aug 19, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@91e18f6). Click here to learn what that means.
The diff coverage is 0%.

Impacted Files Coverage Δ
pkg/skaffold/build/cache/retrieve.go 63.29% <0%> (ø)

Copy link
Contributor

@balopat balopat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A minor nit to make the logs less scary - otherwise LGTM

since we aren't erroring out, red is a bit aggressive.
@priyawadhwa priyawadhwa merged commit ae89619 into GoogleContainerTools:master Aug 22, 2019
@priyawadhwa priyawadhwa deleted the caching branch August 22, 2019 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes priority/p0 Highest priority. We are actively looking at delivering it.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--cache-artifacts fails when there is no local docker daemon
4 participants