Enhance cache strategy with board-specific cache keys #1777
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.
Summary:
This PR refines the caching strategy used in the
Compile Library
GitHub Actions workflow by making cache keys board-specific. Previously, caches forpip
andPlatformIO
were shared across all board configurations, which could lead to cache conflicts or inefficiencies. Now, each board (e.g.,nodemcuv2
,lolin32
) has its own unique cache, improving cache hits and reducing build times.Changes:
pip
andPlatformIO
to incorporate the board matrix value.Motivation:
This change improves the efficiency of the CI/CD pipeline by ensuring that the cache is appropriately scoped for each board, optimizing build times for different configurations.