[
https://issues.apache.org/jira/browse/CASSANDRA-17930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613600#comment-17613600
]
Derek Chen-Becker commented on CASSANDRA-17930:
-----------------------------------------------
I think there's material evidence (e.g. this ticket) that the current approach
has problems. In the short term, I think we need to just manually turn the
crank to fix up what we can find. What I mean by a long-term driven by a single
config is it would be ideal to have a (simple) way to define a test in one
place, and be able to generate the configurations for CircleCI, Jenkins, and
whatever other CI system we decide to use from that canonical source. I'm not
saying that this ticket is where this happens, I'm just saying a system where
you rely on good intentions to ensure parity is statistically unlikely to
maintain that parity over time.
As for naming, I'm fine taking small incremental steps to fix them, but I do
think they need fixed. I don't see any value in having the names not be the
same between the two systems. If changing the name of a test doesn't otherwise
change or break its behavior, do you have an objection?
> Ensure CircleCI and ASF Jenkins CI are aligned
> ----------------------------------------------
>
> Key: CASSANDRA-17930
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17930
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Derek Chen-Becker
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x
>
>
> As discussed in this
> [thread|https://lists.apache.org/list.html?d...@cassandra.apache.org] the
> Cassandra community wants to see CircleCI and ASF CI being aligned - running
> the same tests, configurations, all tests.
> A few examples of discrepancies we already noticed:
> * utests_system_keyspace_directory run only in CircleCI - CASSANDRA-17145
> * dtest-large run only in Jenkins
> * simulator tests run only in CircleCI
> * In a quick skim I think I didn't see
> [these|https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-dtest-pytest.sh#L84-L89]
> runs too in CircleCI - dtest-offheap, dtest-large, dtest-large-novnode
> * packaging is also only tested in Jenkins as far as I recall
> And these are only a few examples on top of my mind. I am sure we will find
> more. We also need to verify the way we call those tests is correct and
> matches in both CIs. (I was looking to solve similar discrepancy in
> CASSANDRA-17912)
> Some info on our tests suites here -
> [https://cassandra.apache.org/_/development/testing.html,]
> [cassandra-builds repo|https://github.com/apache/cassandra-builds] where our
> test images reside and the Jenkins build scripts, which I already referred
> to.
> CircleCI info can be found in the readme which resides in the in-tree folder
> dedicated to configuration and scripts for Circle CI -
> [https://github.com/apache/cassandra/tree/trunk/.circleci]
>
--
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
