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

error fingerprinting files from sarif report

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • analysis-model
    • Analysis Model API Plugin (analysis-model-api): 12.9.0
      Warnings Plugin (warnings-ng): 11.9.0

      after updating to the specified plugin versions the fingerprinting of files from a sarif report is broken.

      [SARIF] [-ERROR-] Can't create fingerprints for some files:
[SARIF] [-ERROR-] - 'file:///C:/J/workspace/Proj/Test.Tool.MyProj/DummyTest.cs', IO exception has been thrown: java.nio.file.InvalidPathException: Illegal char <:> at index 4: file:///C:/J/workspace/Proj/Test.Tool.MyProj/DummyTest.cs

       

      Maybe the problem was introduced by updating the sarifparser lib.
      The changes made there on Sep 1, 2024 look like they may introduced the problem

       

      Was this introduced by JENKINS-73449?

       

        1. resharper_result.json
          7 kB

          [JENKINS-73933] error fingerprinting files from sarif report

          Kevin Broselge created issue -

          Kevin Broselge added a comment -

          sarif report was generated by jetbrains inspectcode

          Kevin Broselge added a comment - sarif report was generated by jetbrains inspectcode

          Ulli Hafner added a comment -

          It seems that the files contains the type as URI prefix now. Is the whole stack trace visible?

          Any chance to create a small SARIF file that contains such a warning so I can use in it my tests?

          Ulli Hafner added a comment - It seems that the files contains the type as URI prefix now. Is the whole stack trace visible? Any chance to create a small SARIF file that contains such a warning so I can use in it my tests?
          Kevin Broselge made changes -
          Attachment New: resharper_result.json [ 63439 ]

          Kevin Broselge added a comment -

          Sure I added a sample resharper_result.json 

          Kevin Broselge added a comment - Sure I added a sample resharper_result.json  

          Kevin Broselge added a comment -

          sry, we do not have a stacktrace

          Kevin Broselge added a comment - sry, we do not have a stacktrace

          Kevin Broselge added a comment -

          any progress here?
          this is a fatal error for all our builds that got at least one defect which is pretty annoying

          Kevin Broselge added a comment - any progress here? this is a fatal error for all our builds that got at least one defect which is pretty annoying
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]
          Ulli Hafner made changes -
          Labels New: help-wanted newbie-friendly

          Ulli Hafner added a comment -

          No, I had not yet found time to look into this. However, it looks like this can be fixed quite easily in the analysis model project. Interested in providing a PR?

          Ulli Hafner added a comment - No, I had not yet found time to look into this. However, it looks like this can be fixed quite easily in the analysis model project. Interested in providing a PR?

            thebro Kevin Broselge
            thebro Kevin Broselge
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: