MINOR: Reuse Maven build outputs in CI tests#9
Draft
xborder wants to merge 1 commit into
Draft
Conversation
xborder
force-pushed
the
ci-reuse-maven-build-output
branch
from
48e7ced to
956f641
Compare
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 changes the CI test matrix to run Maven tests during the existing
build.shinstall pass instead of runningbuild.shand thentest.shas separate Maven passes.build.shstill skips tests by default, so release and packaging workflows keep the existing behavior. The test workflow opts in withARROW_JAVA_BUILD_SKIP_TESTS=OFF, which lets the Docker, macOS, and Windows jobs compile and test in one reactor pass while preserving the out-of-source build directory and JNI/C Data profile setup.Validation: the Test workflow passed on PR #9 with the single-pass CI path. Control timings are in PR #7.