Repository navigation
ci: do not fail builds when the Docker layer cache is unavailable - #94
Merged
Merged
Conversation
Add ignore-error=true to cache-to: type=gha. BuildKit otherwise fails the build on a cache export error, so a cache backend outage would turn into a red build.
This file contains hidden or 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
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.
Adds
ignore-error=trueto everycache-to: type=ghain this repo.Without it, BuildKit fails the whole build when the cache backend is unavailable, including a failed cache export after the image has built. The cache is an optimisation, so losing it should only make the build slower.
The
self-hosted-linuxrunner pool is moving to a self-hosted Actions cache, which adds a backend that can be down. The flag also covers an outage of GitHub's own cache.No other change. Cache behaviour is the same while the backend is healthy.