NOJIRA: Cache SDKs (#994) - #1007
Merged
sarthak shaha (Sarthak-Shaha) merged 1 commit intoAug 25, 2026
Merged
Conversation
* cache_sdk * cache_sdk * apply comment fixes * workflow dispatch on main/release * draft:update all * delete cache
Michael Duggan (miduggan24)
approved these changes
Aug 19, 2026
chirag-silabs
approved these changes
Aug 19, 2026
chirag-silabs
approved these changes
Aug 19, 2026
sarthak shaha (Sarthak-Shaha)
merged commit Aug 25, 2026
667fa58
into
release_2.10-1.6.1
475 of 476 checks passed
sarthak shaha (Sarthak-Shaha)
deleted the
cache/submodules_release_2.10
branch
August 25, 2026 14:26
This file contains hidden or 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
3 participants
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.
CP : #994
Issue Link:
NOJIRA
Description of Problem/Feature:
We clone the sisdk submodule for each run multiple times ,this is inefficient ( was designed in this was as we keep on bumping with new CoL builds frequently) but worked in past. With intemrittent lfs issues faced by public sisdk/wifisdk repos there's a need to update our dev flow to get reliability in CI.
Description of Fix/Solution:
Cache the SiSDK and WiFi SDK working trees in GitHub Actions instead of cloning + LFS-pulling them in every builder job. Docker images were not used; each submodule bump would require rebuilding and publishing a new image.
The cache key is:
silabs-sdks-${{ runner.os }}-${{ runner.arch }}-${SCOPE}-${SISDK_TAG}-${SISDK_SHA:0:12}-${WIFI_SHA:0:12}SCOPEis the PR base branch (mainorrelease_*) on pull requests, otherwise the branch the workflow runs on. The SiSDK.gitmodulestag is used (WiFi SDK uses the same tag). Gitlink SHAs are included so a pin change still busts the cache if the tag string is unchanged..github/actions/cache-sdksrestores/tmp/silabs-sdks.taron a key match and extracts the two working trees. On a miss it shallow-clones both submodules, LFS-pulls, packs a tarball (no.git), saves the cache, and deletes the tarball.dev-apps-builderhas acache-sdkswarm job (same idea ascache-tools, but this cache is kept for later runs). Builder jobs wait on it, thenbuilder.yamlcalls the same action so they restore instead of each cloning..github/workflows/cache-sdks.yamlseeds the durable cache on push tomain/release_*when.gitmodulesor the two submodule pins change, and onworkflow_dispatchfrom those branches only. After a successful seed it keeps the new cache on that branch, deletes the previous cache on that branch, and deletes leftover PR/feature-branchsilabs-sdks-*caches. Othermain/release_*caches are left alone.A PR that does not change the SDK pins should hit the base-branch cache. A pin-bump PR misses, the warm job creates a PR-scoped cache for that run’s builders, and merge + seed writes the new durable cache on
main/release_*and drops the old one.Future improvement: Find similar mechanism for the tools cache
Testing Done:
caching checked on this PR CI