GH-0: Reuse Maven build outputs in CI tests#8
Closed
xborder wants to merge 1 commit into
Closed
Conversation
This comment has been minimized.
This comment has been minimized.
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
1 participant
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.
This removes the redundant
cleangoals fromci/scripts/test.shso the test step can reuse the Maven build outputs produced byci/scripts/build.sh.The CI flow still runs the same build and test scripts, but
test.shno longer deletes the compiled reactor output immediately before running tests. This avoids recompiling the full project in the main test pass and avoids extra clean rebuilds for the JNI/C Data test passes.Validation: the Test workflow passed on this PR, and the control PR is #7.