[YETUS-1030] Support linecomments in junit

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.14.0
• Component/s: Precommit

Release Note

<!-- markdown -->
The JUnit report output has been changed to support two formats, one generated using line-level and the other being a full report with URLs. By default, line is the default with the exception of Circle CI.

Jenkins users should now be able to process the output with the WarningsNG plug-in to provide better feedback in the Jenkins UI.

• Flags: Important
• Assignee: Allen Wittenauer
• Reporter: Allen Wittenauer
• Created: 16/Oct/20 21:03
• Updated: 02/May/22 17:02
• Resolved: 02/May/22 16:16

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.

Issue Links

• causes: YETUS-1174 missing report name check in junit
• is related to: YETUS-1005 Update Cirrus CI Support
• links to: GitHub Pull Request #268