[SERVER-83437] Investigate adjusting Antithesis execution frequency to reflect commit volume Created: 19/Nov/23  Updated: 02/Jan/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Steve Gross Assignee: [DO NOT ASSIGN] Backlog - DevProd Correctness
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Correctness
Participants:

 Description   

Crazy idea: can we dynamically scale our testing as a function of commit volume?

Note:

  • Antithesis execution frequency is controlled by a cronjob (owned by Antithesis)

  • What criteria to use to adjust the run? Say, run proportionate to the volume of commits to the master branch? Anecdotally, I'm seeing ~30 commits/day on a "typical" day. We could have something like:
    • 0 commits = run none (or very little)
    • 1 - 10 commits = run a little bit
    • 11 - 40 commits = run "normal" load
    • 41+ commits = run "normal", but maybe notify stakeholders that volume is way up.

Generated at Thu Feb 08 06:52:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.