You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (Jira)" <ji...@apache.org> on 2022/05/02 16:05:00 UTC

[jira] [Updated] (YETUS-1030) Support linecomments in junit

     [ https://issues.apache.org/jira/browse/YETUS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated YETUS-1030:
------------------------------------
    Flags: Important

> Support linecomments in junit
> -----------------------------
>
>                 Key: YETUS-1030
>                 URL: https://issues.apache.org/jira/browse/YETUS-1030
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Precommit
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Major
>             Fix For: 0.14.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> With junit, there is a lot of flexibility--almost too much.  With _most_ of the junit processors, our existing output works reasonably well.  For systems like Cirrus CI, if we use a more pytest-like format, then Cirrus will use GitHub Checks Annotations to mark the source tree in GitHub.  However, that pytest-like format looks does not really work for, say, Circle CI.  Therefore, it might be useful to provide a one or more switches to either create one or both types of formats for maximum flexibility.  Doing this will almost certainly be an incompatible change.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)