[
https://issues.apache.org/jira/browse/CASSANDRA-17930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613760#comment-17613760
]
Ekaterina Dimitrova commented on CASSANDRA-17930:
-------------------------------------------------
I just linked CASSANDRA-17671 which I just found in my list, opened long ago
but never got to it. I will unassign it as I won't be able to work on it soon I
think if you or anyone else have cycles to deal with it. With that said, I will
be off until 18th October, I will be happy to get back to these problems when I
am back.
{quote}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.
{quote}
Happy to see a written proposal if you are willing to work on such an
implementation after we fill the short-term goals here. I am sure there are
areas of improvement and that every setup evolves in time but also needs
someone with time to be able to sit and work hard on it. So with that said
happy to see you are interested in this area.
{quote} If changing the name of a test doesn't otherwise change or break its
behavior, do you have an objection?
{quote}
I personally do not have any objections to bring things to aligned names where
it makes sense. My request was just such an improvement to be in a separate
ticket. Thanks for looking into that.
> 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
