fix(ci): Enable caching in consume_release and fix docs#38
Merged
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Co-Authored-By: Claude <claude-opus-4-8>
Skip the ~4 min image build and ~10 min build.sh when the Dockerfile and resolved stack SHAs are unchanged. Co-Authored-By: Claude <claude-opus-4-8>
Co-Authored-By: Claude <claude-opus-4-8>
|
Want your agent to iterate on Greptile's feedback? Try greploops. |
mijovic
approved these changes
Jul 20, 2026
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
2 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.
The 20 mins to run the runloop tests is mostly building the stack, should be easy caching
Greptile Summary
This PR adds two layers of GitHub Actions caching to avoid the ~20-minute stack rebuild on every workflow run: a Docker image cache for the
monad-buildertoolchain image (keyed on the builder Dockerfile) and a compiled artifact cache forinstall/(keyed on the full stack: Dockerfile hash + harness/bft/exec SHAs). It also updates thereleasedefault totests-monad_runloop@latestand adds the harness HEAD SHA to the step output/log.monad-builderimage as a tarball at/tmp/monad-builder.tar, restoring it viadocker loadon a cache hit, so the toolchain rebuild is skipped when thebuilder/Dockerfileis unchanged.install/artifact cache skips thebuild.shinvocation entirely when the exact combination of harness, bft, and exec SHAs plus Dockerfile hash matches a prior run's cached output.Log pinned stackstep now also outputs the harness SHA (previously only bft and exec were captured), which is used as part of theeest-installcache key.Confidence Score: 5/5
Safe to merge — the caching additions are additive and well-isolated, with cache misses falling back to the original build path.
Both new cache layers follow the standard split-restore/save pattern with exact-match keys. The install/ key correctly incorporates all three git SHAs plus the Dockerfile hash, preventing stale cached artifacts. No logic in the test-execution or summarization steps was altered.
No files require special attention.
Important Files Changed
Reviews (3): Last reviewed commit: "ci(consume_release): group GITHUB_OUTPUT..." | Re-trigger Greptile