[ZEPPELIN-6486] Rename the mislabeled "Set up JDK 8" CI step to JDK 11 - #5382
Open
huiseong29 wants to merge 1 commit into
Open
[ZEPPELIN-6486] Rename the mislabeled "Set up JDK 8" CI step to JDK 11#5382huiseong29 wants to merge 1 commit into
huiseong29 wants to merge 1 commit into
Conversation
### What is this PR for? The JDK setup step in the flink-test-and-flink-integration-test job of .github/workflows/core.yml was named "Set up JDK 8" while its java-version was already set to 11. The name was the only thing wrong; anyone reading the workflow or the CI logs would think the job runs on JDK 8. This renames the step to "Set up JDK 11", matching the correctly labeled step elsewhere in the same file. Only the display name changes. A grep across .github/workflows/ confirms this was the only static JDK setup step whose name disagreed with its configured java-version; every other step either pins 11 with a matching name or derives the version from the build matrix. ### What type of PR is it? Improvement ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-6486 ### How should this be tested? grep -rn "Set up JDK 8" .github/workflows/ returns no matches. The renamed step still has java-version: 11 and no other keys changed. ### Questions: * Does the license files need to update? No * Is there breaking changes for older versions? No * Does this needs documentation? No
jongyoul
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
2 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.
What is this PR for?
The JDK setup step in the
flink-test-and-flink-integration-testjob of.github/workflows/core.ymlwas named "Set up JDK 8" while itsjava-versionwas already set to11. The name was the only thing wrong; anyone reading the workflow or the CI logs would think the job runs on JDK 8.This renames the step to "Set up JDK 11", matching the correctly labeled step elsewhere in the same file. Only the display name changes —
java-versionand every other key stay exactly as they are.A grep across
.github/workflows/confirms this was the only static JDK setup step whose name disagreed with its configuredjava-version; every other step either pins 11 with a matching name or derives the version from the build matrix.What type of PR is it?
Improvement
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-6486
How should this be tested?
grep -rn "Set up JDK 8" .github/workflows/returns no matches.The renamed step still has
java-version: 11and no other keys changed.The workflow YAML still parses.
Screenshots (if appropriate)
N/A
Questions: