![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Michal Turek
|
|
Components:
|
sloccount |
|
Created:
|
21/Mar/14 2:16 PM
|
|
Description:
|
most times a build is declared failed, its about compilation issues, or health thresholds or simple scripting error status.
so most times, it has nothing to do with sloc.
the problem is that the failed build has no sloc summary data in the build.xml (it doesn't even coast from the previous non-failed build).
Can be addressed many options
0 - ignore failure state of build
1 - have an ignore failed build status option (many other publisher plugins have this
2 - if can't ignore fail status, at least coast the data from last non failed build
in general, suggest that unless there was a path issues (sloc count file doesn't exist) the results should always be published
|
|
Due Date:
|
18/Apr/14 12:00 AM
|
|
Environment:
|
windows 7
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Greg Moncreaff
|
|
|
|
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.
