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

Link to affected source from a warning does not function

    Details

    • Similar Issues:

      Description

      The "Warnings" tab of Jenkins Findbugs results includes a link to the affected file for each warning. This includes a link, e.g. "JDBCImple_driver.java:274". When following this link, a blank template page shows, e.g. "Content of file JDBCImple_driver.java", but with no content visible.

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Which plug-in versions are you using? Is this the only source that does not show up? Is the source file generated? Is there a corresponding log message in the console log of your job? What is the source path of the warning in the file that is generated from findbugs? What is the path/filename in my findbugs-warnings.xml file in your build folder?

          Show
          drulli Ulli Hafner added a comment - Which plug-in versions are you using? Is this the only source that does not show up? Is the source file generated? Is there a corresponding log message in the console log of your job? What is the source path of the warning in the file that is generated from findbugs? What is the path/filename in my findbugs-warnings.xml file in your build folder?
          Hide
          dfj David Jorm added a comment -

          > Which plug-in versions are you using?

          findbugs 2.0.1 with TODO mvn plugin on Jenkins ver. 1.480.2-SNAPSHOT

          > Is this the only source that does not show up?

          All source links from the jenkin findbugs results fail to show up in the same way.

          > Is the source file generated?

          No.

          > Is there a corresponding log message in the console log of your job?

          No, the job executes with no log messages of note, everything is clean.

          > What is the source path of the warning in the file that is generated from findbugs?

          I am sorry I am having trouble understanding exactly what you mean here. What do you mean by the file that is generated from findbugs? Is that the same as findbugs-warnings.xml ?

          Upon further analysis I can see that the source package does not have findbugs-maven-plugin configured in its POM. Is that a possible cause of this problem?

          Show
          dfj David Jorm added a comment - > Which plug-in versions are you using? findbugs 2.0.1 with TODO mvn plugin on Jenkins ver. 1.480.2-SNAPSHOT > Is this the only source that does not show up? All source links from the jenkin findbugs results fail to show up in the same way. > Is the source file generated? No. > Is there a corresponding log message in the console log of your job? No, the job executes with no log messages of note, everything is clean. > What is the source path of the warning in the file that is generated from findbugs? I am sorry I am having trouble understanding exactly what you mean here. What do you mean by the file that is generated from findbugs? Is that the same as findbugs-warnings.xml ? Upon further analysis I can see that the source package does not have findbugs-maven-plugin configured in its POM. Is that a possible cause of this problem?
          Hide
          drulli Ulli Hafner added a comment -

          Upon further analysis I can see that the source package does not have findbugs-maven-plugin configured in its POM. Is that a possible cause of this problem?

          Which source package? Do you have multiple maven modules?

          I am sorry I am having trouble understanding exactly what you mean here. What do you mean by the file that is generated from findbugs? Is that the same as findbugs-warnings.xml ?

          No, it is the output of the maven-findbug-plugin: it is located in your target folder, findbugsResult.xml or something like that...

          Show
          drulli Ulli Hafner added a comment - Upon further analysis I can see that the source package does not have findbugs-maven-plugin configured in its POM. Is that a possible cause of this problem? Which source package? Do you have multiple maven modules? I am sorry I am having trouble understanding exactly what you mean here. What do you mean by the file that is generated from findbugs? Is that the same as findbugs-warnings.xml ? No, it is the output of the maven-findbug-plugin: it is located in your target folder, findbugsResult.xml or something like that...
          Hide
          drulli Ulli Hafner added a comment -

          Please attach the findbugs output file from your build so I can see if the filenames are correctly set.

          Show
          drulli Ulli Hafner added a comment - Please attach the findbugs output file from your build so I can see if the filenames are correctly set.

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              dfj David Jorm
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: