-
Bug
-
Resolution: Won't Fix
-
Minor
-
-
8.0.0
Filtration feature of warning-ng 7.0.0 or above version is not working
Steps invoked:
recordIssues tools: [taskingVx(name: 'Tasking ctc', pattern: '**/*.ec')],
filters: files,
healthy: 0 ,
unhealthy: 100 ,
minimumSeverity: 'HIGH'
After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and
hyperlink on the file having issues are also disabled.
[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues
Entire post processing is missing, if warning ng 7.0.0 or above version is used.
The same functionality is working fine for warning-ng 6.1.1 or below version
[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] [-ERROR-] Can't resolve absolute paths for some files: [Tasking ctc ] [-ERROR-] Can't create fingerprints for some files: [Tasking ctc ] [-ERROR-] - 'D:/Jenkins/shubhamTest/workspace/Playground/HIL_Interface/Test_entire_pipeline/SW/APP/CD/SF/OsSf/ABC/src/Test.c', provided encoding 'UTF-8' seems to be wrong [Tasking ctc ] [-ERROR-] - 'D:/Jenkins/shubhamTest/workspace/Playground/HIL_Interface/Test_entire_pipeline/SW/APP/CD/SF/OsSf/ABC/src/Test1.c', provided encoding 'UTF-8' seems to be wrong [Tasking ctc ] Post processing issues on 'FRVSF56M' with source code encoding 'UTF-8' [Tasking ctc ] Resolving absolute file names for all issues in workspace 'D:\Jenkins\shubhamTest\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW' [Tasking ctc ] -> 211 resolved, 1 unresolved, 1 already resolved [Tasking ctc ] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files) [Tasking ctc ] -> resolved module names for 596 issues [Tasking ctc ] Resolving package names (or namespaces) by parsing the affected files [Tasking ctc ] -> resolved package names of 213 affected files [Tasking ctc ] Applying 322 filters on the set of 596 issues (547 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/223/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #223'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #222' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 0, new: 49, fixed: 596 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 49 issues (found 49 new issues, fixed 596 issues)
- relates to
-
JENKINS-60148 Result log is modified after attaching the action.
-
- Resolved
-
[JENKINS-60417] Print log if post processing has been skipped
That would be very helpful. It makes sense to set a breakpoint here and step through the code. Maybe an exception occurs: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/steps/IssuesScanner.java#L101
The root cause for the failure of post processing step is the availability of some empty files in the directory which is matching with the regex pattern provided in the report file pattern text field.
Empty files are considered as an error, and due to this postProcess method is skipped
I think till warning-ng 6.1.1 version, empty files are not considered as an error.
Thanks for finding the problem! Does it work now when you refine your regex?
I just removed all the empty files from the directory whose name is matching with the regex and then the plugin works fine. if even a single empty file is present in the directory the complete post processing is skipped and logger output is not shown
Hi drulli
Just wanted to know when can i expect the fix for this issue.
This is not on my priority list. If you are interested in providing a PR please let me know.
Post processing feature is skipped/not working when any empty file matches with the pattern.
Issue is not fixed in warning-ng-8.0.0 version
Hafner, I am trying to find the root cause for this issue.
As this issue occurs in all the version of warning-ng plugin above version 6.1.1, so i will start debugging the code of warning-ng 7.2.2 (latest version).
i'll update you, once the root cause is identified