• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • warnings-ng-plugin
    • Jenkins 2.303.1, warnings-ng-plugin 9.5.0 on Windows 10 or Windows Server 2016

       When performing the recordIssues pipeline step below

        recordIssues(
                    enabledForFailure: false,
                    aggregatingResults: true,
                    tools: [
                            java(),
                            mavenConsole(),
                            checkStyle(),
                            taskScanner(highTags: 'FIXME', normalTags: 'TODO', includePattern: '**/*.java',  excludePattern: 'target/**/*')
                     ]
         )

       I get the following error in the Jenkins console for the job.

      java.nio.file.InvalidPathException: Illegal char <:> at index 2: /D:/Jenkins/workspace/mavenskipNotifications-false/src/main/java/simple/HelloWorld.java
      	at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
      	at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
      	at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
      	at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
      	at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
      	at java.nio.file.Paths.get(Paths.java:84)
      	at io.jenkins.plugins.analysis.core.util.AffectedFilesResolver$RemoteFacade.isInWorkspace(AffectedFilesResolver.java:188)
      	at io.jenkins.plugins.analysis.core.util.AffectedFilesResolver$RemoteFacade.isInWorkspace(AffectedFilesResolver.java:184)
      	at io.jenkins.plugins.analysis.core.util.AffectedFilesResolver.copyAffectedFilesToBuildFolder(AffectedFilesResolver.java:122)
      	at io.jenkins.plugins.analysis.core.util.AffectedFilesResolver.copyAffectedFilesToBuildFolder(AffectedFilesResolver.java:106)
      	at io.jenkins.plugins.analysis.core.steps.IssuesScanner.copyAffectedFiles(IssuesScanner.java:170)
      	at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcessReport(IssuesScanner.java:121)
      	at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:97)
      	at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:765)
      	at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:728)
      	at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:697)
      	at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:1109)
      	at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:1067)
      	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)

       This error does not occur with Jenkins 2.249.3 and warnings-ng-plugin 8.4.4.

          [JENKINS-66815] Error running the java format

          Mario Jauvin added a comment -

          drulli do you think it would be possible to have a junit test run on windows to catch such errors in the future.  I know most CI pipelines are run on Linux but maybe this kind of slipped through the cracks because it is windows.

          Mario Jauvin added a comment - drulli  do you think it would be possible to have a junit test run on windows to catch such errors in the future.  I know most CI pipelines are run on Linux but maybe this kind of slipped through the cracks because it is windows.

          Ulli Hafner added a comment -

          All tests run on Windows, macOS and Unix. Here simply the test is missing.

          Ulli Hafner added a comment - All tests run on Windows, macOS and Unix. Here simply the test is missing.

          Mario Jauvin added a comment -

          I presume you closed it because it is duplicate of JENKINS-66738?  Could we add an additional JUnit test for this case?

          Mario Jauvin added a comment - I presume you closed it because it is duplicate of JENKINS-66738 ?  Could we add an additional JUnit test for this case?

          Ulli Hafner added a comment -

          Yes, I closed it since it is duplicate. Feel free to add yourself as watchee of JENKINS-66738. And yes, I will not accept a PR for JENKINS-66738 without any test case.

          Ulli Hafner added a comment - Yes, I closed it since it is duplicate. Feel free to add yourself as watchee of JENKINS-66738 . And yes, I will not accept a PR for JENKINS-66738 without any test case.

            drulli Ulli Hafner
            marioja Mario Jauvin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: