-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Java 25 for CI builds #11155
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
base: main
Are you sure you want to change the base?
Java 25 for CI builds #11155
Changes from 8 commits
f0d4f3a
0464bea
6e08c5a
600e956
ad39770
01ba91f
8ffcfe9
124e00e
823ec32
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,9 +3,12 @@ | |
| goal= | ||
| if [ "$RDBMS" == "h2" ] || [ "$RDBMS" == "" ]; then | ||
| # This is the default. | ||
| goal="preVerifyRelease" | ||
| # Settings needed for `preVerifyRelease` execution - for asciidoctor doc rendering | ||
| export GRADLE_OPTS=-Dorg.gradle.jvmargs='-Dlog4j2.disableJmx -Xmx4g -XX:MaxMetaspaceSize=768m -XX:+HeapDumpOnOutOfMemoryError -Duser.language=en -Duser.country=US -Duser.timezone=UTC -Dfile.encoding=UTF-8' | ||
| # - special check for Jenkins CI jobs where we don't want to run preVerifyRelease | ||
| if [[-n "$CI_SYSTEM" && "$CI_SYSTEM" != "jenkins"]]; then | ||
| goal="preVerifyRelease" | ||
| # Settings needed for `preVerifyRelease` execution - for asciidoctor doc rendering | ||
| export GRADLE_OPTS=-Dorg.gradle.jvmargs='-Dlog4j2.disableJmx -Xmx4g -XX:MaxMetaspaceSize=768m -XX:+HeapDumpOnOutOfMemoryError -Duser.language=en -Duser.country=US -Duser.timezone=UTC -Dfile.encoding=UTF-8' | ||
| fi | ||
|
Comment on lines
5
to
11
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you wanted Though this begs the question: shouldn't calling There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I understand what you are asking, that's what happens - now (once this check is correct). Previously,
Previously, each of those would trigger There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was suggesting moving this out of this script and directly into the GH Actions script where it's needed. We can just call: Yes in practice that's the same -- except if calling build.sh locally. |
||
| elif [ "$RDBMS" == "hsqldb" ] || [ "$RDBMS" == "hsqldb_2_6" ]; then | ||
| goal="-Pdb=hsqldb" | ||
| elif [ "$RDBMS" == "mysql" ] || [ "$RDBMS" == "mysql_8_0" ]; then | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder what's the history behind this and how bad it is to lose it... checking
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the reason: #hibernate-orm-dev > JDK builds @ 💬
TLDR: people will unknowningly using JDK 18+ APIs if we don't have a job that compiles the main code with JDK 17.
So I'd recommend something like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the s390x bit aside, this is for the most part working.
As for this desire to run one job with mainJdkVersion=17, there are 2 "problems"...
ci/build.shalways accounts for H2 using the problematic tasks. Your "something that skips javadoc" would need to get accounted for there. That's easy, but for completeness..-Porm.jdk.min=17for this one job. Coupled with the solution for (1), we aren't building the Javadoc so no harm, no foul.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact, for all of these H2 jobs from Jenkins we should always just skip javadoc generation. Stated more correctly, for these jobs from Jenkins we should treat them like the non-H2 jobs from GH workflow in terms of executing just
ciCheckinstead ofciCheck preVerifyReleaseThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll try to hack something but this Jenkinsfile syntax is bizarre to me :)