![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Ulli Hafner
|
|
Components:
|
analysis-core, checkstyle, findbugs, pmd, warnings |
|
Created:
|
26/Jul/13 4:38 PM
|
|
Description:
|
If the anaysis plugin has a threshold that is set to mark the build as unstable no entry is put in the build console log to show why the build is marked as unstable.
This causes some confusion to users, but also means it is not simple to integrate with the "Build Failure Analyser" so that the reason for the unstable project is immediately obvious.
It would be nice if the there was a line
"[plugin] Build has more failures that the threshold amount - marking unstable."
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
teilo
|
|
|
|
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.
