-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
Windows Server 2008
When there are no FxCop warnings, FxCop deletes the report file.
Hudson interprets this a a problem, when it may be exactly what we want.
My project has no FxCop warnings, so it gets a stormy cloud because no FxCop report file were found.
[JENKINS-5264] no FxCop report may mean no warnings to display
Workflow | Original: JNJira [ 135353 ] | New: JNJira + In-Review [ 174293 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
but it may also indicate that the fxCop failed/crashed, that's why I think current behavior is correct
you can easily force fxCop to generate empty file with /fo switch