[CASSANDRA-15712] Introduce MIDRES config in CircleCI

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta1, 4.0
• Component/s: CI, Test/dtest/python, Test/unit
• Labels: CI
• Change Category: Quality Assurance
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/6755487dcd58797de00ee99e26adc71479e7c1c0

Test and Documentation Plan

• config.yml.MIDRES with the discussed configuration was created using a new generate_midres.sh script with patch config-2_1.yml.mid_res.patch.

• readme.md updated

[trunk ]

[Java11 CI run]

[Java8 CI run]

• Assignee: Ekaterina Dimitrova
• Reporter: Kevin Gallardo

Authors

Ekaterina Dimitrova

Reviewers

Brandon Williams

• Created: 10/Apr/20 15:14
• Updated: 03/Jan/21 17:03
• Resolved: 09/Jun/20 17:16

Description

From document: https://gist.github.com/newkek/bb79dccbe7d2f5e41b2a3daac3858fde

We have identified that the current HIGHRES configuration seems to require resources that might not bring the best cost efficiency to the build.

We have also identified several "good compromise" configurations that allow to get decent performance out of the test suites, without going all out on the big config.

It seems it would be useful for a lot of people to have this available as a config.yml.MIDRES configuration in the .circleci folder. This way we do not need to argue on modifying the HIGHRES configuration so as to not impact the people already using it, but can still have easy access the "compromise" config.