![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Tomas Westling
|
|
Components:
|
build-failure-analyzer |
|
Created:
|
11/Oct/14 11:57 AM
|
|
Description:
|
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.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Thomas De Schampheleire
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
