perf: cache conformance image builds - #127
Merged
Merged
Conversation
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Contributor
Author
|
/conformance |
Signed-off-by: lucarlig <luca.carlig@ibm.com>
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
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
target/directory across source-mode Docker buildscf-integration0.2.1Normal Linux CI still uses the prebuilt artifact path. The cache accelerates local/source builds without trying to copy an incompatible macOS
target/binary into Linux.Results
make conformance: 136.35s, down from 364.88sVerification
actionlintdocker buildx build --check --build-context prebuilt=target/debug --file docker/Dockerfile .--helpsmoke testmake -n conformancemake -n conformance-blessmake conformancewith the locally built 0.2.1 CLIDepends on contextforge-org/contextforge-dev-tools#12. The remaining routed failure is the control-plane strict-modern resource-sync issue tracked in IBM/mcp-context-forge#6485.