-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate Java cudf jar build with statically linked dependencies #10578
Automate Java cudf jar build with statically linked dependencies #10578
Conversation
…d-in-docker-for-native
Signed-off-by: Gera Shegalov <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
Codecov Report
@@ Coverage Diff @@
## branch-22.06 #10578 +/- ##
================================================
+ Coverage 86.30% 86.34% +0.03%
================================================
Files 140 140
Lines 22255 22280 +25
================================================
+ Hits 19207 19237 +30
+ Misses 3048 3043 -5
Continue to review full report at Codecov.
|
Co-authored-by: Jason Lowe <[email protected]>
- and fix bug of CUDF_CPP_BUILD_DIR parameter being ignored Signed-off-by: Gera Shegalov <[email protected]>
…d-in-docker-for-native
Signed-off-by: Gera Shegalov <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
…d-in-docker-for-native
Made local host's .m2 customizable via |
@gpucibot merge |
This PR automates cudf jar build via build.sh . It uses java CI centos7 Docker image to build a portable jar from the source checked out on the host. The Docker container is run as a normal non-root user https://docs.docker.com/engine/install/linux-postinstall/
Examples:
allow overriding GPU architectures with ALL, NATIVE, some subset.
Drop GDS from the image
Adds parallelism to the libcudfjni build, removes
make
hardcodingFix: don't disregard
CUDF_CPP_BUILD_DIR
passed to MavenUse a dedicated CUDF_CPP_BUILD_DIR value to avoid corrupting interactions with
build.sh libcudf