Improve layer caching by moving apk commands up #12834
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
|
/werft run 👍 started the job as gitpod-build-mads-improve-layer-caching.2 |
|
/werft run 👍 started the job as gitpod-build-mads-improve-layer-caching.3 |
|
It is only 4 secs faster though even with caching. |
1 task
1 task
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.
Description
This moves the☺️
apkabove theCOPYinstructions so that we don't invalidate the layers whenever the contents of the files changesRelated Issue(s)
Fixes #12828
How to test
The Werft build should still succeed. In gitpod-build-mads-improve-layer-caching.3 you can see it did indeed use the cached layer for the
apkcommand.Release Notes
Documentation
N/A
Werft options: