[CASSANDRA-15651] Jenkins tests to use testclasslist where possible (like CircleCI)

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.17, 3.0.21, 3.11.7, 4.0, 4.0-alpha4
• Component/s: Build, CI, Test/unit
• Labels: CI
• Change Category: Quality Assurance
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/fa403bb7210de650d6068cee1cb7e4e26ba777bb and https://github.com/apache/cassandra-builds/commit/399a8a0c87489aea236b240ca0edaf781c1c4966 and https://github.com/apache/cassandra-builds/commit/571b2ed35655e6bc13e0

Test and Documentation Plan

jenkins CI, and testing against local jenkins installation

• Assignee: Michael Semb Wever
• Reporter: Michael Semb Wever

Authors

Michael Semb Wever

Reviewers

David Capwell

• Created: 21/Mar/20 11:19
• Updated: 15/May/20 08:53
• Resolved: 28/Mar/20 10:00

Description

Following up on CASSANDRA-15639
 make all the jenkins test jobs run in the same manner.

This standards the approach across test jobs and to CircleCI, and will make it easier to parallelise test runs later on.

Issue Links

• relates to: CASSANDRA-15639 Jenkins build for jvm test should use testclasslist to support parameterized tests