-
New Feature
-
Resolution: Unresolved
-
Major
-
None
Currently, the build failure analyzer plugin requires the user to explicitly define a match expression for each failure.
However, many jobs already produce a JUnit result file, where the different testcases are listed, and failed ones are indicated as such.
It would be great if the build failure analyzer plugin could also use this JUnit file, and automatically report a failure based on the name of the failed testcase (as mentioned in the JUnit result file).
This avoids users having to create redundant match expressions as the testcases itself already know when something failed.
A particular case where this is useful is when using the Build Monitor plugin, which has support for Build Failure Analyzer to display the cause of failed builds.
This is my use case: some integration tests test business logic where registry keys are used.
Sometimes there are problems accessing the registry:
Caused by: java.util.prefs.BackingStoreException: Could not open windowsregistry node Software\JavaSoft\Prefs at root 0x80000001.
This environment problem should be detected and displayed with an description different from other failing tests.
The regexp in the given example: .*Could not open windowsregistry node.*