-
New Feature
-
Resolution: Fixed
-
Minor
-
None
Disclaimer: I have already posted this issue as a question on Stackoverflow, but unfortunately got no feedback there.
Unfortunately, although the warnings are collected and displayed, I cannot trace them back to the source code. The overview shows the correct file path and the file still exists in the file system after the build.
When I click on the file to investigate the individual issues, the filename and line are displayed, but I can't click on it to look at the location in the code.
According to the plugin's documentation, warnings should actually also be displayed in the code if they affect a specific line, for example.
I'm using the iar and the iarCstat plugin like this:
success { dir("${BUILD_DIR}") { recordIssues( tools: [ iar(), iarCstat(pattern: "${BUILD_DIR}\\cstat\\cstat_log.txt") ] ) } }
Can anyone tell me if I am using the plugin incorrectly or if this problem is known? I could not find anything about it...
- is blocked by
-
JENKINS-66810 Use case insensitive matching on Windows
- Open
- links to