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

Violations plugin requires relative paths, pylint creates absolute paths

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • violations-plugin
    • None

      I'm using pylint to create parseable output of my python source code and the violations plugin to display the results in hudson. This works well for statistics, i.e. the number of errors will show up, but in the violations plugin, when you click on any file, it will display "No violations found". I figured out that this problem exists because pylint writes absolute filenames (starting with /home/myuser/.hudson), but the violation plugins requires the filenames to be relative to the workspace directory. As a workaround I added a sed call to my build step:
      sed -i s#.*workspace/## pylint-hudson.txt
      When I modify the pylint-results like this, the violations plugin works as expected.

          [JENKINS-8333] Violations plugin requires relative paths, pylint creates absolute paths

          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
            c089 c089
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: