[Java] fix broken publish layers step - #532
Merged
Merged
Conversation
# Conflicts: # java/publish-layers.sh
sharvath-newrelic
changed the title
sharvath-newrelic
marked this pull request as ready for review
August 4, 2026 21:30
jasonjkeller
approved these changes
Aug 5, 2026
obenkenobi
approved these changes
Aug 5, 2026
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
3 participants
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.
The "Publish staging layers (java25)" step in publish-java.yml is failing in CI.
publish-staging-java25 rebuilt the layer a second time via build-java25-arm64/build-java25-x86, which run ./gradlew packageLayer directly on the GitHub Actions runner. That path uses the repo's checked-in, unpatched Gradle wrapper (8.6), because the wrapper patch to Gradle 9.1.0 (needed for JDK 25 support) only exists inside Dockerfile.java25's build context. publish-staging-java25 now checks that the artifacts built by the prior step already exist and publishes them directly instead of rebuilding.