[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690437#comment-17690437
]
Brandon Williams commented on CASSANDRA-18106:
----------------------------------------------
Testing on older branches to ensure nothing broke:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18106-3.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/861/workflows/7c29fe94-dbf4-42eb-ab01-f010259f2f2d]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-18106-3.11]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/862/workflows/40e324e2-42b8-49d1-b15a-36d644d306a2]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18106-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/859/workflows/d4c4d4e1-72be-426a-b74e-9f67682d4e20],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/859/workflows/8c4a4db1-eae0-43f6-9480-2f118e8988b9]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-18106-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/860/workflows/05c06d65-9ae5-461c-a0df-e6f900c5d202],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/860/workflows/b7ebdda7-451a-486c-adb4-8908a8ff9124]|
> Update CCM for JDK17 and revise current JDK detection strategy
> --------------------------------------------------------------
>
> Key: CASSANDRA-18106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18106
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.x
>
>
> As part of CASSANDRA-16895 initial POC an initial version of CCM patch was
> created. This needs to be revisited and reviewed
> Recently we closed CASSANDRA-18039 which brought questions, probably we need
> to revise how we detect JDK versions in CCM and whether it is correct. To the
> best of my knowledge there are certain tests in the repo around that and they
> pass so my guess is we need to revise just the strategy and maybe document it
> explicitly or consider if we want any changes to be applied. Also, we need to
> be careful with breaking changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
