![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Tomas Westling
|
|
Components:
|
build-failure-analyzer-plugin |
|
Created:
|
04/Nov/14 5:17 PM
|
|
Description:
|
Currently the only supported analyzing source is jenkins job console.
In context of integration testing I would like to detect communication or configuration errors wich are not subjekt of the test itself.
To check this i would like to use a multi-line regex for failure details, failure stacktrace, failure stderr and failure stdout.
sample 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.
I started implementation (see https://github.com/jan-feindt/build-failure-analyzer-plugin/commit/3964ff86b2ca0bfc2ed45c8a5d28220a8385580b). I think I misused FoundIndication.matchingFile to change the URL-Part from consoleFull to testReport (see TestResultFailureReader line 142). This should be solved in any other way.
The implementation requires a Post-build action to 'publish JUnit test report', because it depends on the Jenkins API on TestResult objects.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jan Feindt
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
