[
https://issues.apache.org/jira/browse/CASSANDRA-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700937#comment-17700937
]
Ekaterina Dimitrova edited comment on CASSANDRA-18247 at 3/16/23 3:16 AM:
--------------------------------------------------------------------------
CASSANDRA-18106 is committed.
*Summary:*
* Added separate CircleCI configuration files for JDK11+17 plus created a
respective generate_11_and_17.sh script. The differentiator for all new files
is they all end up with "_11_and_17" suffix as part of their names. The new
script operates the new config files in the way generate.sh operates on the old
JDK8+11 configuration files. Why I chose to do it that way? - I believe this
will make it easy when the time to switch to 11+17 come.
* Updated the readme. I would appreciate constructive feedback from reviewers
if it reads well or it is unclear and confusing.
* Currently we miss upgrade tests because we do not have JDK11 upgrade tests
yet
* The simulator still does not support JDK17 so I added only JDK11 simulator
tests
* Current table of all test failures with respective ticket numbers will be
opened on CASSANDRA-16895 after this one gets committed.
* I also plan to send email update to @dev when this gets committed. It will
inform people that the new configuration is available.
Patch -
[https://github.com/apache/cassandra/commit/88dc2a6c7690472d78b428384793e383f37499dc]
CI run
[#2318|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18247-trunk-v2]
, started new run of j11_cqlsh_dtests_py311
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2318/workflows/7eb1fe27-71d0-46d9-9feb-4cdb65e0153e/jobs/19642]
- there was a git clone issue in the previous run
Ticket move to PATCH AVAILABLE pending on clean CI, tests were just started
was (Author: e.dimitrova):
CASSANDRA-18106 is committed.
*Summary:*
* Added separate CircleCI configuration files for JDK11+17 plus created a
respective generate_11_and_17.sh script. The differentiator for all new files
is they all end up with "_11_and_17" suffix as part of their names. The new
script operates the new config files in the way generate.sh operates on the old
JDK8+11 configuration files. Why I chose to do it that way? - I believe this
will make it easy when the time to switch to 11+17 come.
* Updated the readme. I would appreciate constructive feedback from reviewers
if it reads well or it is unclear and confusing.
* Currently we miss upgrade tests because we do not have JDK11 upgrade tests
yet
* The simulator still does not support JDK17 so I added only JDK11 simulator
tests
* Current table of all failures and respective tickets will be opened on
CASSANDRA-16895 after this one gets committed.
* I also plan to send email update to @dev when this gets committed. It will
inform people that the new configuration is available.
Patch -
[https://github.com/apache/cassandra/commit/88dc2a6c7690472d78b428384793e383f37499dc]
CI run
[#2318|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18247-trunk-v2]
, started new run of j11_cqlsh_dtests_py311
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2318/workflows/7eb1fe27-71d0-46d9-9feb-4cdb65e0153e/jobs/19642]
- there was a git clone issue in the previous run
Ticket move to PATCH AVAILABLE pending on clean CI, tests were just started
> Add CircleCI config files for J11+J17
> -------------------------------------
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 5.x
>
>
> Based on the direction of [this
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy],
> I would like to propose CircleCI config files which can be used to test
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in
> another ticket, to be opened soon)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
