build.yml: use cache for Docker build envs #4367
Open
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
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.
after 1st run, the cache will be used. the docker* workflows will build in under 15 mins , example @ https://github.com/plowsof/monero-gui/actions/runs/11232245513
threads bumped to 4
this is not a fancy docker layer caching method, which isnt a concern as if any of the Dockerfile.* are modified then the build env will be built from scratch.
every github repo has 10GB of cache to play with
1st run: https://github.com/monero-project/monero-gui/actions/runs/11232547452
2nd: https://github.com/monero-project/monero-gui/actions/runs/11233958792