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

Maven warnings details are broken

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-plugin
    • None
    • Linux

      Clicking on any maven warning details results in an error as below. It doesn't seem that spaces in the path are to blame, but it could be it.

      Content of file workspace

      01 Copying the source file '/var/lib/jenkins/jobs/Labs Dev Tools Build/workspace' from the workspace to the build folder '/var/lib/jenkins/jobs/Labs Dev Tools Build/builds/2014-03-11_14-52-52/workspace-files/eff088c9.tmp' on the Jenkins master failed.
      02 Is the file '/var/lib/jenkins/jobs/Labs Dev Tools Build/workspace' a valid filename?
      03 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]//var/lib/jenkins/jobs/Labs Dev Tools Build/workspace'
      04 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace//var/lib/jenkins/jobs/Labs Dev Tools Build/workspace'
      05 java.io.FileNotFoundException: /var/lib/jenkins/jobs/Labs Dev Tools Build/workspace (Is a directory)
      06 at java.io.FileInputStream.open(Native Method)
      07 at java.io.FileInputStream.<init>(FileInputStream.java:146)
      08 at hudson.FilePath$34.invoke(FilePath.java:1797)
      09 at hudson.FilePath$34.invoke(FilePath.java:1792)
      10 at hudson.FilePath.act(FilePath.java:916)
      11 at hudson.FilePath.act(FilePath.java:889)
      12 at hudson.FilePath.copyTo(FilePath.java:1792)
      13 at hudson.plugins.analysis.core.HealthAwareRecorder.copyFilesWithAnnotationsToBuildFolder(HealthAwareRecorder.java:398)
      14 at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:336)
      15 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333)
      16 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      17 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
      18 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
      19 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030)
      20 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
      21 at hudson.model.Run.execute(Run.java:1690)
      22 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
      23 at hudson.model.ResourceController.execute(ResourceController.java:88)
      24 at hudson.model.Executor.run(Executor.java:246)

        1. screenshot.png
          screenshot.png
          102 kB
        2. screenshot1.png
          screenshot1.png
          86 kB
        3. screenshot2.png
          screenshot2.png
          124 kB

          [JENKINS-22139] Maven warnings details are broken

          Ulli Hafner added a comment -

          Which parser? Why is the workspace found as conflicting file?

          Ulli Hafner added a comment - Which parser? Why is the workspace found as conflicting file?

          Arcadiy Ivanov added a comment - - edited

          This is for Maven warnings parser. See attached screenshot.

          >> Why is the workspace found as conflicting file?
          I'm not really sure what you're asking, unfortunately. I suspect Warnings plugin is confused about the location of the log files within the workspace and picks workspace directory itself.

          Arcadiy Ivanov added a comment - - edited This is for Maven warnings parser. See attached screenshot. >> Why is the workspace found as conflicting file? I'm not really sure what you're asking, unfortunately. I suspect Warnings plugin is confused about the location of the log files within the workspace and picks workspace directory itself.

          Arcadiy Ivanov added a comment -

          Also note, there are weird paths like "$JENKINS_HOME/[job-name]//var/lib/jenkins/jobs/Labs Dev Tools Build/workspace" mentioned for some reason.

          Arcadiy Ivanov added a comment - Also note, there are weird paths like "$JENKINS_HOME/ [job-name] //var/lib/jenkins/jobs/Labs Dev Tools Build/workspace" mentioned for some reason.

          Ulli Hafner added a comment -

          And what are the warnings in the log that have been parsed?

          Ulli Hafner added a comment - And what are the warnings in the log that have been parsed?

          Arcadiy Ivanov added a comment - - edited

          I don't think type matters, because none of them actually work.
          Screenshots of warnings are attached.

          Arcadiy Ivanov added a comment - - edited I don't think type matters, because none of them actually work. Screenshots of warnings are attached.

          Ulli Hafner added a comment -

          But what is the actual maven line in your console log? Can you please show me that, it is used as basis for the parser.

          Ulli Hafner added a comment - But what is the actual maven line in your console log? Can you please show me that, it is used as basis for the parser.

          Ulli Hafner added a comment - - edited

          I think I understand now what's going on, there is no filename given at all. Actually the console log should be shown when clicking on the link...

          Ulli Hafner added a comment - - edited I think I understand now what's going on, there is no filename given at all. Actually the console log should be shown when clicking on the link...

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          analysis-collector
          http://jenkins-ci.org/commit/analysis-suite-plugin/193401128ce4ecd00772d9bf5616d6b757d86fb8
          Log:
          [FIXED JENKINS-22139] Don't expand empty path with workspace root.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: analysis-collector http://jenkins-ci.org/commit/analysis-suite-plugin/193401128ce4ecd00772d9bf5616d6b757d86fb8 Log: [FIXED JENKINS-22139] Don't expand empty path with workspace root.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/main/java/hudson/plugins/analysis/core/ParserResult.java
          http://jenkins-ci.org/commit/analysis-core-plugin/3ddc1d7912a072efb8173c1ce527089de403db70
          Log:
          [FIXED JENKINS-22139] Don't expand empty path with workspace root.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/ParserResult.java http://jenkins-ci.org/commit/analysis-core-plugin/3ddc1d7912a072efb8173c1ce527089de403db70 Log: [FIXED JENKINS-22139] Don't expand empty path with workspace root.

          Arcadiy Ivanov added a comment -

          Thanks a lot! When is this fix getting into a released plugin version?

          Arcadiy Ivanov added a comment - Thanks a lot! When is this fix getting into a released plugin version?

            drulli Ulli Hafner
            arcivanov Arcadiy Ivanov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: