[
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645382#comment-17645382
]
Ekaterina Dimitrova commented on CASSANDRA-17869:
-------------------------------------------------
{quote}Both upgrade test types already have in-place definitions of what
versions can be, and are to be, upgraded from and to. So it makes sense to not
enforce the JDK used at the test level, but via the build.xml (so we actually
verify that there's a JDK in common that all upgrade paths can operate on)
{quote}
+1
{quote}But… it's unclear to what the purpose of the JAVA8_HOME and JAVA11_HOME
variables are for? Given the jdk used for the tests comes down the JAVA_HOME
variable anyway, and building bc JAVA11_HOME doesn't happen anymore…
{quote}
I was thinking we need to dig a bit also in CCM what it uses, how and why.
There were some recent concerns brought while looking into running CQLSHLIB
tests in CI and that is what made me think about that but I didn't have the
chance to do it so far. I think we probably need separate ticket. I will open
one now.
{quote}Why have anything in trunk ? (There was a discussion about it recently,
but i can't find it…)
{quote}
Honestly, I cannot remember which discussion you are referring to.
> Add JDK17 option to cassandra-builds (build-scripts and jenkins dsl) and on
> jenkins agents
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17869
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17869
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
>
> Add JDK17 option to cassandra-builds build-scripts, they only currently
> support options {{8}} and {{1}}.
> Add JDK17 to the matrix axes in the jenkins dsl.
> Ensure JDK17 is installed on all the jenkins agents.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
