[
https://issues.apache.org/jira/browse/YETUS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-1030:
------------------------------------
Description: 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. (was: With junit, there is a lot
of flexibility--almost too much.)
> 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
> Priority: Major
>
> 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.3.4#803005)
