Actually I don't know excatly since when, but for about 2 weeks I'm facing this exception over and over again:

2019-10-30 14:24:55 [Project 1] Searching for all files in '<WS_PATH>\<PIPELINE_NAME>' that match the pattern 'Outputs\<Project1>\Build.log'
2019-10-30 14:24:55 [Project 1] -> found 1 file
2019-10-30 14:24:55 [Project 1] Successfully parsed file <WS_PATH>\<PIPELINE_NAME>\Outputs\<Project1>\Build.log
2019-10-30 14:24:55 [Project 1] -> found 2 issues (skipped 1 duplicate)
2019-10-30 14:24:59 [Project 1] Post processing issues on 'Master' with source code encoding 'UTF-8'
2019-10-30 14:24:59 [Project 1] Resolving absolute file names for all issues in source directories '[<WS_PATH>\<PIPELINE_NAME>]'
2019-10-30 14:24:59 [Project 1] -> 2 resolved, 0 unresolved, 0 already resolved
2019-10-30 14:24:59 [Project 1] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
2019-10-30 14:24:59 [Project 1] -> resolved module names for 2 issues
2019-10-30 14:24:59 [Project 1] Resolving package names (or namespaces) by parsing the affected files
2019-10-30 14:24:59 [Project 1] -> resolved package names of 2 affected files
2019-10-30 14:24:59 [Project 1] No filter has been set, publishing all 2 issues
2019-10-30 14:24:59 [Project 1] Creating fingerprints for all affected code blocks to track issues over different builds
2019-10-30 14:24:59 [Project 1] -> created fingerprints for 2 issues
2019-10-30 14:24:59 [Project 1] Copying affected files to Jenkins' build folder '<JENKINS_PATH>\jobs\<PIPELINE_NAME>\builds\315\files-with-issues'
2019-10-30 14:24:59 [Project 1] -> 0 copied, 2 not in workspace, 0 not-found, 0 with I/O error
2019-10-30 14:24:59 [Project 2] Searching for all files in '<WS_PATH>\<PIPELINE_NAME>' that match the pattern 'Outputs\<Project2>\Build.log'
2019-10-30 14:24:59 [Project 2] -> found 1 file
2019-10-30 14:24:59 [Project 2] Successfully parsed file <WS_PATH>\<PIPELINE_NAME>\Outputs\<Project2>\Build.log
2019-10-30 14:24:59 [Project 2] -> found 141 issues (skipped 141 duplicates)

[...] skipped due to earlier failure(s) [... ]

java.nio.file.InvalidPathException: Illegal char <*> at index 44: <PATH>/Src*** <PATH>/Source/file.c
at java.base/sun.nio.fs.WindowsPathParser.normalize(Unknown Source)
at java.base/sun.nio.fs.WindowsPathParser.parse(Unknown Source)
at java.base/sun.nio.fs.WindowsPathParser.parse(Unknown Source)
at java.base/sun.nio.fs.WindowsPath.parse(Unknown Source)
at java.base/sun.nio.fs.WindowsFileSystem.getPath(Unknown Source)
at java.base/java.nio.file.Path.of(Unknown Source)
at java.base/java.nio.file.Paths.get(Unknown Source)
at io.jenkins.plugins.analysis.core.util.AbsolutePathGenerator.resolveAbsolutePath(AbsolutePathGenerator.java:118)
at io.jenkins.plugins.analysis.core.util.AbsolutePathGenerator.resolveAbsoluteNames(AbsolutePathGenerator.java:94)
at io.jenkins.plugins.analysis.core.util.AbsolutePathGenerator.run(AbsolutePathGenerator.java:74)
at io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.resolveAbsolutePaths(IssuesScanner.java:321)
at io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:274)
at io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:246)
at hudson.FilePath.act(FilePath.java:1078)
at hudson.FilePath.act(FilePath.java:1061)
at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:126)
at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:110)
at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:629)
at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:581)
at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:563)
at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:973)
at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:936)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Finished: FAILURE

I have not changed my previously working pipline script for some time. I just used to update the Jenkins and its plugins from time to time. Right now, I don't have an explanation as even the path nor the file contains any non-ASCII chars or other vorbidden once. The only thing I can tell is, that it happends, when "RecordIssus" is used to generade some charts out of a build log file.

The jenkins script looks like this:

echo "Parsing compiler warnings..."
recordIssues(
id: 'Build_Binary',
name: 'Build Binary',
sourceCodeEncoding: 'UTF-8',
enabledForFailure: true,
aggregatingResults: true,
tools:
[
groovyScript(
id: 'Project_1',
name: 'Project 1',
parserId: 'myParser',
pattern:'04_Outputs
<Project1>
Build.log',
reportEncoding:'UTF-8'
),
groovyScript(
id: 'Project_2',
name: 'Project 2',
parserId: 'myParser',
pattern:'Outputs
<Project2>
Build.log',
reportEncoding:'UTF-8'
),
groovyScript(
id: 'Project_3',
name: 'Project 3',
parserId: 'myParser',
pattern:'Outputs
<Project3>
Build.log',
reportEncoding:'UTF-8'
),
groovyScript(
id: 'Project_4',
name: 'Project 4',
parserId: 'myParser',
pattern:'Outputs
<Project4>
Build.log',
reportEncoding:'UTF-8'
),
gcc(
id: 'Project_5',
name: 'Project 5',
pattern:'Outputs
<Project5>
Build.log',
reportEncoding:'UTF-8'
)
]
)

I'm sorry for the obfuscation but I'm not allowed to share exact content. (I tried to keep the sense of the messages.) If you need more information please let me know.

Thanks for your time.