[
https://issues.apache.org/jira/browse/CASSANDRA-17930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612724#comment-17612724
]
Ekaterina Dimitrova commented on CASSANDRA-17930:
-------------------------------------------------
{quote} * An ideal outcome (albeit longer-term) would be a single test
configuration source that could drive generation of both systems{quote}
If you say one config for both - they are different software with different
config. In that sense we already have them using the same testing images,
splitting tests (CircleCI has its own way but similar outcome), pointing to the
same targets and running tests with the same parameters. So they are equal
under the hood. Now, you will say why this ticket then? Because in time not all
suites were added everywhere and sometimes people did changes to one without
realizing that the other one needs it too. We need to fill that gap.
{quote} * The Circle and Jenkins configurations are in separate repositories,
which adds a little complexity to that task{quote}
Check previous answer :)
{quote} * In the short term, some auditing automation would be helpful{quote}
Do you have anything particular in mind?
{quote}Naming appears to differ for the same set of tests between Circle and
Jenkins
{quote}
I think those not marked for novnode are with vnode but I agree it might be
confusing or not immediately obvious for someone new.
I guess we can do something about that but in a separate ticket. While you
think It is "just" small name change, talking from experience, it is never just
and leads to a chain of other changes. Small incremental changes are always
better when talking about CI and infra.
{quote}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
{quote}
I'd say please check the tests by looking into ant targets, job names for
example and do not change naming at this point.
I guess now when you know what node/no vnode is in each CI and j8 and j11 are
easy to recognize, that should not be a problem. But please, do let me know if
I am missing something or if something I point to is not clear.
Thanks
CC [~mck] for awareness :)
> 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
