jason810496 opened a new pull request, #69794: URL: https://github.com/apache/airflow/pull/69794
related: - follow-up of: https://github.com/apache/airflow/pull/69239#issuecomment-4925259828 - PR: #69411 ## Why #69239 (java_sdk e2e mode) and #69411 (lang-SDK k8s test) solved the same cold-Gradle-build problem two different ways: containerized builds with a repo-local cache vs. host-toolchain builds with salted home-dir caches. This converges the e2e `java_sdk` mode on the #69411 native-toolchain convention. ## How - CI exports `LANG_SDK_NATIVE_TOOLCHAIN=true` (the same switch the k8s job uses) so the conftest invokes the host `./gradlew` instead of `docker run eclipse-temurin:17-jdk` — the build helpers take a `native` flag mirroring the #69411 k8s helpers. This drops the per-run toolchain-image pull and the container workarounds (`--network=host` lock handover, `HOME` override). Local runs keep the containerized build, so a dev host still needs no JDK. - The JDK comes from `actions/setup-java`, versioned by the existing `java-sdk-version` build-info output, as `k8s-tests.yml` already does. - The Gradle cache moves to the default `~/.gradle` with a salted key (`e2e-java-sdk-gradle-v1-`, bump to invalidate), kept separate from the k8s job's key since the e2e tree carries ~1GB of Spark the k8s job never needs. --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes, with help of Claude Code Fable 5 following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
