[
https://issues.apache.org/jira/browse/CASSANDRA-17939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617880#comment-17617880
]
Josh McKenzie commented on CASSANDRA-17939:
-------------------------------------------
Couple nits on the review (looks like the old top level repeat count was left
in the script help output and readme.md) but otherwise +1.
I'll make a note for us to create some follow up tickets about massaging the
output of generate.sh on the following fronts:
# Tuning parallelism levels per job (David's findings indicate there's a more
optimal / tighter bound for this)
# Renaming of jobs to be more indicative of their function
# Updating documentation w/guidance on using circle ([how to
commit|https://cassandra.apache.org/_/development/how_to_commit.html],
[testing|https://cassandra.apache.org/_/development/testing.html])
Thanks for being patient w/all my probing on this Andres. I've been using this
ecosystem quite a bit in the past year and have accumulated some opinions as a
user. :)
> CircleCI: Automatically detect and repeat new or modified JUnit tests
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-17939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17939
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Andres de la Peña
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> The purpose of this ticket is adding a new CircleCI job that automatically
> detects new or modified test classes and runs them repeatedly. That way we
> wouldn't need to manually specify those tests with {{.circleci/generate.sh}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
