Releases: melexis/warnings-plugin
Adding xmlrunner parser for Python unit test
XMLRunner reports errors on output, but they are not logged inside the reports. New checker is deployed to warnings plugin to parse the output and fail the build when there are errors in XMLRunner. So far it only checks for errors and does not parse reports for the failures.
0.2.0
add json configparser for allowing more flexible and traceable configuration
Bugfix: Empty logfile should fail the check
There was an issue described in #54 where empty logfile passed the empty input to checker and return was a success - which is faulty.
Bugfix: Ignore return value with command option
We were ignoring a return value of the program we executed with --command
flag. This release fixes that and it also adds an optional argument where ignoring program return value is expected behavior (then warnings are parsed and decision is taken on that).
Be aware that ignoring command return value can have a side effect where command fails, does not produce any output, therefor there are no warnings, so plugin marks it as passed.
Execute target command directly via plugin
The new feature enables you to execute your target command directly through plugin, eliminating pipe-ing to log files. It uses simple subprocess so the data from plugin is not printed line by line (as it happens), but it is buffered and printed afterwards. Since plugin is used in CI only, this should not pose a big problem.
WARNING: Possibility to break backwards compatibility is that now is any arguments that come after command or log file (first non --
argument) are considered command arguments (and not plugin arguments).
Release 0.0.10
Improved regex for sphinx for parsing warnings from e.g. mlx.traceability plugin
Release 0.0.9
fix #42 for 0.0.8 to be not usable
Release 0.0.8
support multiple log-file arguments (wildcarded),
add verbose flag,
return count of warnings,
use junitparser for JUnitChecker,
start with integration test cases
Release 0.0.7
Merge pull request #25 from melexis/issue_22 Fix #22: different main approach
Release 0.0.6
Merge pull request #16 from melexis/junit-failures JUnit failures counter