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

Casey Brotherton commented on YETUS-333:
----------------------------------------

This would be ideal:
https://jira.atlassian.com/browse/JRASERVER-65575

As the vote table isn't only for Jira, and that request hasn't been satisfied, 
though...
here are some observations:
1)  If there is a -1, the precommit test will likely be re-run.
2)  For failures, the most important is -0, and -1 scores.
3)  There is the possibility of adding a "header" to the vote table.
4)  There are multiple finalreport functions.
5)  The number of lines in a vote table are determined by personality.  
( For example, Yetus' own vote table is rather small. )

Suggestion:  For jira, bugzilla, github, and htmlout final reports, 
when there is at least one failure in the vote table, 
and the number of votes is above a configurable limit with a default of 10, 
print a summary report.
The summary report will have the number of total passed votes
the number of passed votes below a header ( If one exists )
Any failed, or -0 vote lines.

Sounds like a good plan?
In this way, a neophyte should still get the total count.
Summaries would only show in bug systems, not in console output
If the neophyte persevered and submitted a patch without negative votes, then 
they would see the whole vote table with all of the checks.


> Shorter comments for pre-commit builds only highlighting areas of concern
> -------------------------------------------------------------------------
>
>                 Key: YETUS-333
>                 URL: https://issues.apache.org/jira/browse/YETUS-333
>             Project: Yetus
>          Issue Type: Improvement
>            Reporter: Karthik Kambatla
>
> YETUS is pretty comprehensive in the pre-commit checks it runs. As we add 
> more checks, the comments themselves become fairly long. In the interest of 
> keeping the JIRA scrolls short, it might help to have shorter comments that 
> highlight any concerning areas along with a link to the comprehensive 
> checklist. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to