[CASSANDRA-18593] CircleCI: Add separate approval step for oa utests on separate workflows

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: CI
• Bug Category: Correctness - API / Semantic Definition
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 5.x

Source Control Link

https://github.com/apache/cassandra/commit/83a331624674755ba90ad19bf206c351b5fcdff5

Test and Documentation Plan

Multiple CircleCI configs are tested here:

• j8-j11 free
• j8-j11 paid
• j11-j17 free
• j11-j17 paid

• Assignee: Andres de la Peña
• Reporter: Andres de la Peña

Authors

Andres de la Peña

Reviewers

Berenguer Blasi

• Created: 13/Jun/23 12:15
• Updated: 12/Sep/23 13:02
• Resolved: 16/Jun/23 12:10

Description

CASSANDRA-14227 added new j*_utests_oa jobs to run unit tests with the new, not-default "oa" sstable format. Those tests depend on the start_j*_unit_tests approval step on the separate workflows.

However, the separate workflow is meant to allow running jobs individually, and having a common approval step for both j*_unit_tests and j*_utests_oa prevents us from doing so. That's the case for example of the development of CASSANDRA-18504, where I want to run a single unit test job without caring about the specialization, but the common approval step forces me to run both jobs, duplicating the costs. An example run can be seen here.

I think that j*_utests_oa should have its own separate approval step, the same way that j*_utest_cdc, j*_utest_fqltool, j*_utest_compression or j*_utest_system_keyspace_directory have their own approval step.

Issue Links

• is caused by: CASSANDRA-14227 Extend maximum expiration date
• links to: GitHub Pull Request #2413