[
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676715#comment-17676715
]
Ekaterina Dimitrova commented on CASSANDRA-17869:
-------------------------------------------------
For the record, while testing both JDK11 and 17 we caught a bug in my branch,
that was fixed. Thanks [~mck]
Things shifted during rebase and I was focused on the Java 17 tests so I didn't
notice earlier.
I left a few questions/comments in the PR but overall it looks good to me!
I think the main question is do we want to commit this now with a toggle that
will switch later when we switch trunk from J8+J11 to J11+J17, or just have it
ready for when the time comes. I leave It up to you Mick to decide. If we
commit it now we will need to test all branches. If we leave it for later, that
also seems ok to me because I do not expect cassandra-builds to get many change
in the meantime.
> 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: 4.x
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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]
