![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Tomas Westling
|
|
Components:
|
build-failure-analyzer |
|
Created:
|
17/Apr/13 12:13 PM
|
|
Description:
|
Right now the build failure analyzer accepts 1 line of regular _expression_ as an indicator for failure cause. However, in my experience many failures causes need more than 1 line to be identified.
For example, an error message may be "Error number=1", meaning download failed, but there could be many things being downloaded, so the download link/description in the console log 3 lines above the error message is necessary for useful identification of the problem.
Allowing more than one line per failure cause indication could potentially give significant improvement to this plugin.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Baris Batiege
|
|
|
|
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/groups/opt_out.
