dongjoon-hyun opened a new pull request, #645:
URL: https://github.com/apache/spark-kubernetes-operator/pull/645

   ### What changes were proposed in this pull request?
   
   This PR updates the builder stage base image of 
`build-tools/docker/Dockerfile` to `gradle:9.4.1-jdk26-noble`.
   
   ```diff
   -FROM gradle:9.4.1-jdk25-noble AS builder
   +FROM gradle:9.4.1-jdk26-noble AS builder
   ```
   
   ### Why are the changes needed?
   
   Since SPARK-56088, the project's Gradle Java toolchain is set to 
`JavaLanguageVersion.of(26)` (`build.gradle`), and all build jobs in 
`.github/workflows/build_and_test.yml` already run on JDK 26. However, the 
Docker builder stage still ran Gradle on JDK 25, which forced Gradle to 
auto-provision JDK 26 inside the container during every image build.
   
   Aligning the builder image with JDK 26:
   - Removes the in-container JDK 26 auto-provisioning step.
   - Matches the CI build environment for consistent and reproducible image 
builds.
   - Reduces external network dependency at build time.
   
   The runtime stages (`azul/zulu-openjdk-alpine:26` for `jlink` and 
`alpine:3.23` for the final image) and the Java 21 bytecode target 
(`options.release = 21`, `jdeps --multi-release 21`) are unchanged.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Pass the CIs and manually built the Docker image.
   
   ```
   $ gradle buildDockerImage
   $ docker run --rm apache/spark-kubernetes-operator:0.9.0-SNAPSHOT java 
--version
   ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 4.7


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to