[
https://issues.jenkins-ci.org/browse/JENKINS-12792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160902#comment-160902
]
alexlombardi commented on JENKINS-12792:
----------------------------------------
I am seeing a vartiation of this as well.
As long as the violation occurs in a .vb file and has lines of code associated
with it, I am able to drill down into the details and see the code section in
Jenkins. You can then hover over that code to get details of what the violation
was and what the remedy is.
Drilling down into the details for violations against classes or namespaces
however, which do not contain line(s) of code entries in the generated XML,
produce a red bordered triangle with a exclamation sign in it indicating
something went wrong. In the past this produced a report of what the error was
even if there was no associated code.
> Violation Plugin display [no report] for FxCop
> ----------------------------------------------
>
> Key: JENKINS-12792
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12792
> Project: Jenkins
> Issue Type: Bug
> Components: violations
> Affects Versions: current
> Reporter: Arun Mariappan Karunanithi
> Assignee: peterkittreilly
> Priority: Minor
> Attachments: jenkins-violation.png
>
>
> I am using the FxCop 1.36 command line to generate the Violation report. When
> there are no Violation in the specified .dll then the FxCop return "No
> messages written" and no output file written.
> So the violation plug-in displays as "Fxcop No reports" in the violation
> graph. It's not an big issue but the Build Icon changed to Thunder
> Icon.(Check the attachment)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
