Optimize E2E workflow: build ToolHive binary only once #1937
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
Optimizes the E2E tests workflow by building the ToolHive binary only once and reusing it across all matrix jobs, significantly reducing CI execution time.
Changes
build-binaryjob: Creates a separate job that builds the ToolHive binary once using the existing build processe2e-testsjob to depend onbuild-binaryvianeeds: build-binaryBenefits
core,mcp,proxy-mw) can now run in parallel after the single build completesWorkflow Structure
Before:
e2e-tests(3 parallel jobs, each building binary)After:
build-binary→e2e-tests(3 parallel jobs using shared binary)Testing
The workflow maintains the same test execution pattern and environment variables. The only change is how the binary is obtained (artifact download vs. local build).