[
https://issues.apache.org/jira/browse/CASSANDRA-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629883#comment-17629883
]
Brandon Williams commented on CASSANDRA-17854:
----------------------------------------------
bq. i'm a bit confused as to why CASSANDRA-17885 doesn't fix this
Originally I wanted to backport CASSANDRA-17581 to the older branches that
lacked it, which were being pulled in by dtests and breaking them against
active branches. That turned out to not be feasible so we
[agreed|https://issues.apache.org/jira/browse/CASSANDRA-17885?focusedCommentId=17603180&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17603180]
to instead change the dtests to accommodate the older branches. This was
done, for the active branches where those tests are being run, but not for
every past branch since we don't run tests for all of those. If someone does
want to run those older branches, they will need to get around CASSANDRA-17581
somehow on their own (but that's not terribly difficult; just use an older JDK.)
> Add JDK17 to our test docker images
> -----------------------------------
>
> Key: CASSANDRA-17854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17854
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
>
> In preparation to support JDK 17 I want to add JDK 17 to our test images to
> enable our CIs for testing with JDK 17
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
