• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: analysis-model, warnings-ng-plugin
• Labels:

  None

[JENKINS-55373] Warnings Next Generation: Error on accessing 'MSBUILD' file

Florian Hug created issue - 2019-01-01 16:41

Florian Hug made changes - 2019-01-01 16:42

Description

Original: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154 |[https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt]|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt)] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|[https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java])|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java)]   However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

New: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|[https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt]|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|[https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java])|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java)]   However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

Florian Hug made changes - 2019-01-01 16:43

Description

Original: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|[https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt]|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|[https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java])|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java)]   However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

New: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|[https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt]] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|[https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java])|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java)]   However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

Florian Hug made changes - 2019-01-01 16:44

Description

Original: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|[https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt]] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|[https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java])|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java)]   However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

New: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java] However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

Florian Hug made changes - 2019-01-01 16:44

Description

Original: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java] However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

New: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java]) However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

Florian Hug made changes - 2019-01-01 16:49

Description

Original: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java]) However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

New: When using the warnings-ng-plugin to parse an MSBUILD output as described in analysis-model [issue20154|https://github.com/jenkinsci/analysis-model/blob/2fc7a2ad6f430baa626e2dd6d772ccc8de853fae/src/test/resources/edu/hm/hafner/analysis/parser/issue20154.txt] the expected outcome is that the filename 'MSBUILD' is recognized. (see [here|https://github.com/jenkinsci/analysis-model/blob/48ee0fefe9d45f3a65f999f3080e3c4d89529523/src/test/java/edu/hm/hafner/analysis/parser/MsBuildParserTest.java#L214] Line 214) However, as a consequence the publishIssues step in warnings-ng-plugin tries to resolve the absolute path and create fingerprints for the file 'MSBUILD', which of course fails and pollutes the console outwith with ERROR messages. {code:java} [MyLib] [ERROR] Can't resolve absolute paths for some files: [MyLib] [ERROR] - MSBUILD [MyLib] [ERROR] Can't create fingerprints for some files: [MyLib] [ERROR] - 'MSBUILD', IO exception has been thrown: java.nio.file.NoSuchFileException: MSBUILD [MyLib] Resolving absolute file names for all issues [MyLib] -> 0 resolved, 1 unresolved, 0 already resolved [MyLib] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/.../builds/130 [MyLib] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error {code}   From my point of view, an easy workaround would be to remove any 'MSBUILD' entry before processing the files, or to not add the dummy 'MSBUILD' file entry at the beginning (This would however be a breaking change). Any chance to get this fixed?

Ulli Hafner made changes - 2019-01-02 13:42

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Fixed but Unreleased [ 10203 ]

Ulli Hafner made changes - 2019-01-15 23:29

Released As		New: warnings-ng 2.0.0, analysis-model-api 2.0.0
Status	Original: Fixed but Unreleased [ 10203 ]	New: Resolved [ 5 ]