[
https://issues.apache.org/jira/browse/YETUS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342954#comment-17342954
]
Allen Wittenauer edited comment on YETUS-1109 at 5/12/21, 1:30 AM:
-------------------------------------------------------------------
At $DAYJOB, I've got Apache Yetus running all of its static checkers under
Jenkins and writing the results back to Github annotations for about 20 repos.
So... time? lack of documentation? Runs taking too long? Too many results?
Bugs?
Apache Hadoop tried to do it but that build is so utterly broken that it was
doomed to failure.
was (Author: aw):
At $DAYJOB, I've got Apache Yetus running all of its static checkers under
Jenkins and writing the results back to Github Checks for about 20 repos.
So... time? lack of documentation? Runs taking too long? Too many results?
Bugs?
Apache Hadoop tried to do it but that build is so utterly broken that it was
doomed to failure.
> Posting new comments to a Github PR should hide all previous buildbot comments
> ------------------------------------------------------------------------------
>
> Key: YETUS-1109
> URL: https://issues.apache.org/jira/browse/YETUS-1109
> Project: Yetus
> Issue Type: Improvement
> Components: Precommit
> Reporter: Nick Dimiduk
> Priority: Major
>
> A quality-of-life request in absence of YETUS-633. When the robot posts a new
> comment with a build result, it should go back and mark as hidden all
> comments that it has previously made. This makes it easier for humans to find
> comments made by other humans throughout the history, while also being clear
> on what the latest build result is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
