You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/10/26 01:04:00 UTC

[jira] [Updated] (CASSANDRA-17930) Ensure CircleCI and ASF Jenkins CI are aligned

     [ https://issues.apache.org/jira/browse/CASSANDRA-17930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekaterina Dimitrova updated CASSANDRA-17930:
--------------------------------------------
    Description: 
As discussed in this [thread|https://lists.apache.org/list.html?dev@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]

EDIT: More findings:
 *  burn tests missing in CircleIC
 * cqlshlib in 3.11.
 * 4.0+ we also need in-jvm JDK8 with 11, cqlshlib JDK8 with 11. 

 

  was:
As discussed in this [thread|https://lists.apache.org/list.html?dev@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]

 


> 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?dev@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]
> EDIT: More findings:
>  *  burn tests missing in CircleIC
>  * cqlshlib in 3.11.
>  * 4.0+ we also need in-jvm JDK8 with 11, cqlshlib JDK8 with 11. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org