[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695910#comment-17695910
]
Ekaterina Dimitrova edited comment on CASSANDRA-18106 at 3/2/23 10:14 PM:
--------------------------------------------------------------------------
Ok, thank you for confirming. So I see the case that we are also saving on
resources that way. As you run tests on every version, you won't be repeating.
What I mean - running the full test 3.11 to 5 and then the test 4 or 4.1 to 5,
skipping the overlap and running only what you need.
Looking into CASSANDRA-18285, I think you actually reminded me there that there
is also the case of 4.0 to 4.1 with 11 residing on 4.0. Another layer of
duplication?
was (Author: e.dimitrova):
Ok, thank you for confirming. So I see the case that we are also saving on
resources that way. As you run tests on every version, you won't be repeating.
What I mean - running the full test 3.11 to 5 and then the test 4 or 4.1 to 5,
skipping the overlap and running only what you need.
Looking into CASSANDRA-18285, I think you actually mentioned that there is also
the case of 4.0 to 4.1 with 11 residing on 4.0. Another layer of duplication?
> 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]
