Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12095

Violations plugin not reporting fxcop details

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • violations-plugin
    • Jenkins v 1.440 on Windows Server 2008 / Violations Plugin 0.7.10

      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.

        1. jenkins-screenshot.jpg
          jenkins-screenshot.jpg
          96 kB

          [JENKINS-12095] Violations plugin not reporting fxcop details

          alexlombardi added a comment - - edited

          I am seeing the same issue. When you drill down into details for FxCOp (v. 1.36) the page is blank.

          alexlombardi added a comment - - edited I am seeing the same issue. When you drill down into details for FxCOp (v. 1.36) the page is blank.

          tyler smith added a comment -

          alexlombardi: Same here. It shows I have 2 violations and when i click one it takes me to a blank page.

          tyler smith added a comment - alexlombardi: Same here. It shows I have 2 violations and when i click one it takes me to a blank page.

          Gregory Nofi added a comment - - edited

          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.

          Nevermind. We tried downgrading to 0.7.9 and the problem still existed. It turned out that we were missing a directory between $WORKSPACE and the root directory in our pep8/pylint report.

          Gregory Nofi added a comment - - edited 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. Nevermind. We tried downgrading to 0.7.9 and the problem still existed. It turned out that we were missing a directory between $WORKSPACE and the root directory in our pep8/pylint report.

          Mark Waite added a comment -

          The violations plugin is deprecated. It has an unresolved security vulnerability. The last commit to the source code repository was over 7 years ago. Closing the issue as "Won't fix"

          Mark Waite added a comment - The violations plugin is deprecated. It has an unresolved security vulnerability. The last commit to the source code repository was over 7 years ago. Closing the issue as "Won't fix"

            peterkittreilly peterkittreilly
            schneina Nick Schneider
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: