|
||||||||
|
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.
I'm not sure if such feature can be useful. How do you call the SLOCCount tool, before or after the build? I'm using most often:
In all three cases the sloccount command won't be executed and sloccount.sc file generated if the build fails. Make, Ant and shell (in Jenkins) most often stops the processing on first error. So processing the non-existent or outdated sloccount.sc data is not reasonable.
0 - ignore failure state of build
-> Yes, this is possible, but you have to somehow satisfy that sloccount.sc contains valid data. E.g. generate it after checkout and before the build - does anyone do that?
1 - have an ignore failed build status option (many other publisher plugins have this
-> Exactly the same as 0 above.
2 - if can't ignore fail status, at least coast the data from last non failed build
-> Why? No information is added anywhere if we copy the data. The plugin already skips the failed builds if e.g. compares current and previous results.
To be honest I don't see this feature much useful, but let's discuss...