Test shared Maven workflow for Java builds - #2545
Draft
msarahan wants to merge 2 commits into
Draft
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Member
Author
|
/ok to test b7c0f0b |
Member
Author
|
/ok to test 3a76e60 |
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.
Posted by Codex (GPT-5) on behalf of @msarahan. Treat this message as LLM-generated.
Why
cuVS currently reconstructs the Java build matrix and invokes shared-workflows/custom-job.yaml separately for cuvs-java and cuvs-lucene. This draft exercises the shared Maven build contract proposed in rapidsai/shared-workflows#626 and shows the downstream configuration reduction for a repository with two ordered Maven coordinates.
This is an integration experiment, not a merge-ready production change. PR CI is intentionally reduced to the two Maven builds so it does not spend capacity rebuilding unrelated C++, Python, wheel, Rust, Go, documentation, or devcontainer outputs while the shared contract is being evaluated.
What changes
Deliberate test scope
The production build workflow keeps all existing non-Java deliverables and dependencies. Only this draft PR workflow is reduced to Java and Lucene, using published libcuvs packages so no C++ or Python package build is required.
Validation
The full pre-commit suite passes with Rust 1.95, including ruff, mypy, dependency-file generation, ShellCheck, yamllint, and zizmor. The cmake hooks passed while noting that no local rapids-cmake formatting configuration was present; no CMake files are changed.
DO NOT MERGE: this PR exists to validate rapidsai/shared-workflows#626 and review the downstream interface.