[
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712499#comment-17712499
]
Michael Semb Wever commented on CASSANDRA-17869:
------------------------------------------------
bq. I can see a few upgrade tests from 3.x versions.
Strictly speaking I think this is out-of-scope. Will look if it is easy to fix…
bq. cassandra-builds changes will affect also previous branches so I guess when
the time to commit anything comes, we should test them that nothing shifted.
Yes, most are already run on the custom jenkins.
bq. … fear there might be places where we still want to consider
CASSANDRA_USE_JDK11 for 4.0 and 4.1
This is not a problem, the grep against java.version.11 works on past code too.
bq. aren't we going to add upgrade tests with JDK 11 also for 4.0 to 4.1?
No. Upgrade tests will use the lowest (default) JDK that is in common. 4.0 and
4.1 share JDK8 so that will be used for that path. I don't see the ROI in
testing additional JDKs here.
> 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
> Fix For: 5.x
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Add JDK17 option to cassandra-builds build-scripts, they only currently
> support options {{8}} and {{11}}.
> 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]
