[ https://issues.jenkins-ci.org/browse/JENKINS-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163143#comment-163143 ]
Gregory Nofi commented on JENKINS-12095: ---------------------------------------- I'm also seeing this, but for pep8 and pylint. I'm not sure if it's related but pep8/pylint per-file view worked before upgrading to 0.7.10. > Violations plugin not reporting fxcop details > --------------------------------------------- > > Key: JENKINS-12095 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12095 > Project: Jenkins > Issue Type: Bug > Components: violations > Affects Versions: current > Environment: Jenkins v 1.440 on Windows Server 2008 / Violations > Plugin 0.7.10 > Reporter: Nick Schneider > Assignee: peterkittreilly > Labels: plugin > Fix For: current > > Attachments: jenkins-screenshot.jpg > > > I'm building a .NET script in which I have a post build step executing a > windows batch command: > fxcopcmd /file:HelloWorld\bin\HelloWorld.dll /out:fxcop-report.xml /s > exit 0 > I have check the 'Violations' option and next to the fxcop XML filename > pattern, I have placed 'fxcop-report.xml' > After the build I know there were 14 violations placed in the xml file, but > I'm not seeing any results in the graph view of the violations, and when I > click on the graph it doesn't even specify out that fxcop was picked up (see > screenshot). > UPDATE: This only affects a maven 2/3 project. If I build a free-style > project, I get the violations to show up. -- 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