Cache IDF and tools for esp32 CI builds #2848
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
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.
Saves time and resources downloading the IDF itself, all its submodules and build tools.
Just need to clear the cache if we update IDF versions.
Total cache used is 5.58GB.
Note: Changed CI builds only to use a shallow clone for IDF (with submodules),
otherwise cache consumed hits 10.25GB which exceeds allowance.
Individually, the IDF size goes from from 1.5GB+ to 250MB.
Most of this is attributable to
components/esp_wifi/libs.Note: Windows esp32 tools come in around 1.1-1.3GB compared with 350-520MB for other OSes.