CI - Cache more of our build outputs #3521
Merged
Conversation
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
… bfops/ci-caching
…ckworklabs/SpacetimeDB into bfops/ci-caching
…ngs take" This reverts commit c3ebef0.
bfops
commented
Nov 17, 2025
bfops
commented
Nov 17, 2025
…new-runner' into bfops/ci-caching
Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.com>
bfops
commented
Nov 18, 2025
jdetter
approved these changes
Nov 19, 2025
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 of Changes
Changes with cache hit:
CI / Smoketests (spacetimedb-runner): 17m -> 10m
CI / Smoketests (windows-latest): 39m -> 31m
CI / Lints: 3m30s -> 2m
unity-testsuite: 23m -> 19m
This included creating a stripped-down
Dockerfilethat only runs SpacetimeDB (as opposed to e.g. building tracy, flamegraphs, etc.). That shaves off about 4-5m on the linux smoketests job.API and ABI breaking changes
No. CI only.
Expected complexity level and risk
2
Testing
Ran existing CI and noted the change in times in the description above