.
> So yeah. I think we'll need to figure out how much coverage is reasonable >> to call something "tested". I don't think it's sustainable for us to have, >> at any given time, 3 branches we test across 3 JDK's each with all our >> in-jvm test suites is it? >> > Correct. For non-upgrade tests, where testing against more than one jdk exists, we should start the conversation of the value of running more than one JDK for all tests per-commit CI, before we go adding a third. I'm not against weekly/fortnightly CI runs, just that it deserves the discussion of cost (it's not necessarily cheaper due to saturation, nor are we a team that has assigned build barons). The actual change is relatively easy, just adding a profile and a jdk element here: https://github.com/apache/cassandra/blob/trunk/.jenkins/Jenkinsfile#L126-L135
