![]() |
|
|
|
|
Change By:
|
Baris Batiege
(17/Apr/13 1:04 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=
ExitCode:
1"
from a shell script
,
meaning download
which normally means the previous command
failed
. If the plugin supported regular _expression_ on multiple lines
,
but there could
this would allow a more accurate failure cause to
be
many things being downloaded, so
identified by reading
the
download link/description in the console log 3
lines
above
before or after
the error message
is necessary for useful identification of the problem
.
Perhaps a user setting on how many lines are allowed to be parsed each time should be provided to limit performance impact.
Allowing more than one line per failure cause indication could potentially give significant improvement to this plugin.
|
|
|
|
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/groups/opt_out.
