[ 
https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093874#comment-17093874
 ] 

Michael Semb Wever commented on CASSANDRA-15729:
------------------------------------------------

Thanks for the review [~dcapwell]. Looks like you jumped a bit in front of me, 
as some of those changes were still wip. Only the stuff 
[here|https://github.com/thelastpickle/cassandra/commit/ed0a7e7e2f3e2a67825b8d560ee9ffbb60983336]
 is ready to go (and needs to go out first in advance).

But I can reply to your comments anyway :-)
The `ant jar` is only temporarily commented out. The `apt install` stuff will 
happen using docker instead. The clean block will get removed (if it doesn't 
get used). The `cassandra-test-report.sh` scripts is available because on the 
line before the `${buildRepo}` (ie cassandra-builds) is cloned. And the 
calculations for the 1MB limit was roughly what I did too. And there's no way 
to know if we over, unless the jenkins email plugin has some of check (before 
sending).

> Jenkins Test Results Report in plaintext for ASF ML
> ---------------------------------------------------
>
>                 Key: CASSANDRA-15729
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15729
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build, CI
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>              Labels: Jenkins
>             Fix For: 4.0-beta
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to