Changed cache scope for container image build #459
Merged
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.
Fixes #457
I'm not entirely sure if this is going to be the best way to do it, but it worth a shot. The idea here is to have one set of cache elements per matrix build. If we consider the way docker uses cached layers during build, there might no need to include the branch and tag name in the scope value:
Because of step one is being constant most of the time, it should work with just the cpu arch as a cache key.