• 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. screenshot1.png
          screenshot1.png
          86 kB
        2. screenshot2.png
          screenshot2.png
          124 kB
        3. screenshot.png
          screenshot.png
          102 kB

          [JENKINS-22139] Maven warnings details are broken

          Arcadiy Ivanov created issue -

          Ulli Hafner added a comment -

          Can you please answer the question of the error message, otherwise I can't help.

          Ulli Hafner added a comment - Can you please answer the question of the error message, otherwise I can't help.

          Ulli - question is meaningless: the logic is trying to copy workspace DIRECTORY into a file. I can't answer it, since it cannot be.

          Arcadiy Ivanov added a comment - Ulli - question is meaningless: the logic is trying to copy workspace DIRECTORY into a file. I can't answer it, since it cannot be.

          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 made changes -
          Attachment New: screenshot.png [ 25535 ]

          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.
          Arcadiy Ivanov made changes -
          Attachment New: screenshot1.png [ 25544 ]
          Attachment New: screenshot2.png [ 25545 ]

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

              Created:
              Updated:
              Resolved: