Details
Description
The Jenkins pipeline builds now aggregate all test reports.
For example:
- https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/
- https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests
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:
- https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E
- https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E
An example plaintext report, to demonstrate feasibility, is available here: https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E
Hurdles:
- 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.
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-15875 Jenkins pipeline small fixes: slack notification body, StabilityTestDataPublisher, archive cassandra-test-report.txt
- Resolved
-
CASSANDRA-16401 Remove the Jenkins plaintext reports
- Resolved