[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava created an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-12-10 09:42 Priority: Critical Reporter: shubham srivastava Filtration feature of warning-ng 7.0.0 or above version is not working 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 Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

Change By: shubham srivastava

Filtration feature of warning-ng 7.0.0 or above version is not working 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. {

{}} {{{ panel} }}{{}}

[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

{ {{ panel} }}

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

{{{panel}}} [Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] Applying 322 filters on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49 issues (found 0 new issues, fixed 0 issues) {{{panel}}}{{}}

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: shubham srivastava

Filtration feature of warning-ng 7.0.0 or above version is not working 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. {panel} [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 {panel} 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   {panel}

[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] * Applying 322 filters * on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49 issues (found 0 new issues, fixed 0 issues) {panel} {{}}

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: shubham srivastava

Filtration feature of warning-ng 7.0.0 or above version is not working 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. {panel} [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 {panel} 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   { {{ panel} }}

[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] Applying 322 filters on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49 issues (found 0 new issues, fixed 0 issues) { {{ panel} }} {{}}

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: shubham srivastava

Filtration feature of warning-ng 7.0.0 or above version is not working 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. {panel} [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 {panel} 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   {panel}

[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49 * issues (found 0 new issues, fixed 0 issues) {panel} {{}}

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: shubham srivastava

Filtration feature of warning-ng 7.0.0 or above version is not working 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. {panel}

[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

{panel} 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   {panel}

[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49* issues (found 0 new issues, fixed 0 issues) {panel} {{}}

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: shubham srivastava

Filtration feature of warning-ng 7.0.0 or above version is not working 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. {panel}

[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

{panel} 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   {panel} [Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49* issues (found 0 new issues, fixed 0 issues) {panel}

{{}}

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

Change By: Ulli Hafner

Filtration feature of warning-ng 7.0.0 or above version is not working 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.

{ panel noformat }

[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

{ panel noformat }

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

{ panel noformat }

[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 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/205/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 #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, 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 49* issues (found 0 new issues, fixed 0 issues)

{ panel noformat }

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: Ulli Hafner

Filtration feature of warning-ng 7.0.0 or above version is not working 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.

{noformat}

[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 {noformat}

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

{noformat} [Tasking ctc ] Successfully parsed -> 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\ TestProject shubhamTest \workspace\Playground\HIL_Interface\Test_entire_pipeline\SW \APP\CD\SYS\Test\out\Test ' [Tasking ctc ] -> 211 resolved, 1 unresolved, 1 already resolved [Tasking ctc ] Resolving module names from module definitions (build . ec xml, pom.xml, or Manifest.mf files) [Tasking ctc ] -> found 594 resolved module names for 596 issues [Tasking ctc ] Resolving package names ( skipped 492 duplicates 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 594 596 issues ( 545 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/ 205 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 # 205 223 '. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline # 2 222 ' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49 0 , new: 0 49 , fixed: 0 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 0 49 new issues, fixed 0 596 issues) {noformat}

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-60417 Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Change By: Ulli Hafner

Filtration feature of warning-ng 7.0.0 or above version is not working

Steps invoked: {noformat} recordIssues tools: [taskingVx(name: 'Tasking ctc', pattern: '**/*.ec')],             filters: files,             healthy: 0 ,             unhealthy: 100 ,             minimumSeverity: 'HIGH' {noformat}

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. {noformat} [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

{noformat} 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   {noformat}

[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) {noformat}

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Are there any exceptions in the Jenkins log? What version of forensics-api and analysis-mode-api do you have installed? Is the build invoked on the master or agent?

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

I didn't find any exception in the log. currently the following version of plugin is installed warning-ng 7.2.2, forensics-api 0.6.1 and Analysis model API 7.0.2 build is invoked on agent   if warning-ng 6.1.1, forensics-api 0.4.1 and Analysis model api 7.0.2 is used. then there is no issue, everything works fine

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

Ulli Hafner Any progress/update on this issue?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

No, I do not have a clue why this fails on your machine. I cannot reproduce this issue locally.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner edited a comment on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

No, I do not have a clue why this fails on your machine. I cannot reproduce this issue locally.

Are you familiar with debugging a Java application? Maybe it makes sense to attach a debugger to your Jenkins instance and see where the process fails...

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above 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

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

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

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

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 https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/steps/IssuesScanner.java#L105   I think till warning-ng 6.1.1 version, empty files are not considered as an error.

Add Comment

[shubhamsrivastava726@gmail.com (JIRA)]

shubham srivastava commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

Ulli Hafner Any update on this ticket?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-60417

Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version

Thanks for finding the problem! Does it work now when you refine your regex?

Add Comment