|
||||||||
|
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/groups/opt_out.
@Pete, that might be a different error. Did you try the FxCopCmd.exe.config changes from the "Common problems" section on https://wiki.jenkins-ci.org/display/JENKINS/FxCop+Runner+Plugin?
The root issue is that the FxCopCmd.exe program is returning error codes when it actually succeeded. Jenkins looks to that return code to figure out if the program was OK or not, and that's a hard to work around without a lot of extra effort for the FxCop-Runner plugin.