Reuse the CI build binary for MCP conformance - #91
Open
lucarlig wants to merge 1 commit into
Open
Conversation
lucarlig
force-pushed
the
user/luca/speed-up-conformance-build
branch
6 times, most recently
from
August 14, 2026 09:25
cd72004 to
98a7793
Compare
Signed-off-by: lucarlig <luca.carlig@ibm.com>
lucarlig
force-pushed
the
user/luca/speed-up-conformance-build
branch
from
August 14, 2026 09:26
98a7793 to
e57ca0b
Compare
lucarlig
marked this pull request as ready for review
August 14, 2026 10:03
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
buildjob as a one-day artifactbuildand consume that artifact from a reusable workflowdev,test, andbenchprofilesWhy
In the motivating Actions run, the local image build took 6m16s of a 7m13s job. Its duplicate release Cargo build took 5m42s, while the actual conformance runner completed in about two seconds.
The regular CI
buildjob already runscargo build --locked --workspace --all-features. The resulting data-plane binary has everything conformance needs; optional test-plugin code remains inactive because the conformance stack does not enable runtime plugins. Reusing that exact output removes the second toolchain setup, dependency installation, Cargo build, and separate Rust cache.Conformance remains a behavioral check using the checked-out PR source. Published production images continue to use the existing fully optimized release build.
Only conformance depends on
build, because it consumes the uploaded binary. Formatting, secrets, Clippy, cargo-deny, cargo-shear, tests, and benchmark compilation remain parallel; their separate runners and job-specific Rust caches do not reuse the build job's target directory.Measured in GitHub Actions
build, including artifact preparation and upload: 36sPassing final run: https://github.com/contextforge-org/contextforge-data-plane/actions/runs/31788072058
Validation
actionlint .github/workflows/ci.yml .github/workflows/mcp_conformance.ymlcargo build --locked --workspace --all-featurescpandstripdocker buildx build --check --target conformance-prebuilt ...Motivating run: https://github.com/contextforge-org/contextforge-data-plane/actions/runs/31783682605/job/94714717793?pr=82