[
https://issues.apache.org/jira/browse/CASSANDRA-17930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612699#comment-17612699
]
Derek Chen-Becker commented on CASSANDRA-17930:
-----------------------------------------------
OK, I think I'm at least familiar enough with both the Jenkins and Circle build
setup scripts to start with some observations:
* An ideal outcome (albeit longer-term) would be a single test configuration
source that could drive generation of both systems
* The Circle and Jenkins configurations are in separate repositories, which
adds a little complexity to that task
* In the short term, some auditing automation would be helpful
* Naming appears to differ for the same set of tests between Circle and
Jenkins. However, this may just be me misunderstanding how either DSL works.
Some examples:
** j8 (Circle) vs jdk_1.8_latest (Jenkins)
** with-vnode (Circle) vs nothing in Jenkins for vnode tests as far as I can
tell
** no-vnodes (Circle) vs novnode (Jenkins)
Is the naming tied to the CI somehow, or could we revise the naming to align
across both? That would at least help with auditing, and I can do it as part of
adding some of the missing tests to either side. Given prior discussion I can
focus on getting the tests missing in Circle if that makes sense
> 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
