The Jenkins pipeline builds now aggregate all test reports.
But Jenkins can only keep a limited amount of build history, so those links are not permanent, can't be used as references, and don't help for bisecting and blame on regressions (and flakey tests) over a longer period of time.
The builds@ ML can provide a permanent record of test results.
This was first brought up in these two threads:
An example plaintext report, to demonstrate feasibility, is available here: https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E
- the ASF mailing lists won't accept html, attachments, or any message body over 1MB.
- packages are used as a differentiator in the final aggregated report. The cqlsh and dtests currently don't specify it. It needs to be added as a "dot-separated" prefix to the testsuite and testcase name.