Add support for JDK EA builds in -Druntime.java=xx #118329
Labels
Comments
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
Pinging @elastic/es-delivery (Team:Delivery) |
|
@ChrisHegarty I addressed this here: #119387 We had already some support for EA runtime java versions but we need to explicitly set the version we wanna support here. |
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this issue
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes elastic#118329 (cherry picked from commit f028340)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this issue
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes elastic#118329 (cherry picked from commit f028340)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this issue
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes elastic#118329 (cherry picked from commit f028340)
elasticsearchmachine
pushed a commit
that referenced
this issue
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
elasticsearchmachine
pushed a commit
that referenced
this issue
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
elasticsearchmachine
pushed a commit
that referenced
this issue
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Improve support for the runtime JDK so that one can specify a JDK EA build to automatically download and run tests with, e.g.
-Druntime.java=24. The URLs are the most awkward part of this! :-(The text was updated successfully, but these errors were encountered: