[
https://issues.apache.org/jira/browse/YETUS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195493#comment-15195493
]
Allen Wittenauer commented on YETUS-333:
----------------------------------------
This one is a tricky issue as there are a lot of topics in play:
* did yetus actually test the correct stuff?
* how do runtimes get reported?
* what is *actually* important?
Someone I discussed this with a few months ago said, effectively: "I want to
see the long output for my own patches but not for anyone else's." Haha.
One solution to this might be that we create an option that only lists 0's and
-1's on bug systems but keep the long output on console. My suspicion is that
this won't make reviews or tests any better and may actually make them worse
since the data isn't staring committers in the face.
> 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.3.4#6332)
