[Tracking] Separate Java build and test in CI
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Summary
Currently, ci/test_java.sh runs both build and test via ./build.sh java. This issue tracks the plan to separate them after the Java CI becomes stable, so that Java tests in CI assume prebuilt artifacts are available and only run tests.
Motivation
- Avoid rebuilding Java bindings in every CI run
- Allow for future use of prebuilt or published Java packages
- Simplify test CI jobs
Planned Work
- Ensure Java artifacts are prebuilt and made available to the test job (via package download)
- Remove
./build.sh javafromci/test_java.sh
Context
This change prepares the path for possibly distributing cuvs-java packages later, and was suggested during review in PR #805.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ci/test_java.sh and ./build.sh java, then review the discussion in PR #805 for the intended Java CI setup. Ensure Java artifacts are available to the test job through package download, remove the build step from ci/test_java.sh, and verify that the test job runs against the prebuilt artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100