[
https://issues.apache.org/jira/browse/YETUS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215229#comment-17215229
]
Allen Wittenauer commented on YETUS-992:
----------------------------------------
So I need some advice.
Upon working on YETUS-1028 to fix the java problem mentioned above, Yetus
itself regularly hits the 10 annotations per step limit when building the full
source tree. They are consumed entirely by checkstyle, which we have marked as
a filtered test. On PRs, one is more likely to see just the relevant filtered
test output that was caused by the change. Another choice might be to provide
a total count and then make a decision based upon that.... that's not
necessarily cheap to do though.
I'm leaning towards filtered tests not getting github annotations. People can
always download the artifact result logs and take a look. This would then push
up the "important" breaks when building a branch or a PR.
Thoughts? Or does this not make any sense? haha. Thanks.
> Create and publish a github action
> ----------------------------------
>
> Key: YETUS-992
> URL: https://issues.apache.org/jira/browse/YETUS-992
> Project: Yetus
> Issue Type: New Feature
> Components: Precommit
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Fix For: 0.13.0
>
> Attachments: GitHub_Marketplace_Developer_Agreement.txt, Screen Shot
> 2020-09-22 at 9.15.22 PM.png
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We should publish a github action for use by the GitHub community. Note that
> in order to do this, we will need a completely separate git repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
