[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Shannon Kerr closed an issue as Fixed Jenkins / JENKINS-56001 NG Warnings plugin pre-pending '/workspace' before agent's workspace Change By: Shannon Kerr Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Shannon Kerr commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace Works great! Thanks for the quick fix! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Shannon Kerr commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace I had to wait for Jenkins builds to clear out so I could restart, but I have it installed and I just kicked off a new build. I'll know where we are shortly. Thank you very much for the super fast turnaround time on this. We are really excited about your Next Gen Warnings plugin. I've already moved our cppcheck to using it and it's working great. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace If you are running the build in parallel with some linux nodes then the /workspace/TinyXml is indeed coming from a parallel log. However this should not matter with the latest version since I fixed detection of absolute paths on Windows so the MSBuild warnings should show up correctly. Did you try the new version already? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Shannon Kerr commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace In this case we're building on a Windows machine with VS, so there is no "make Entering directory output". When I call "recordIssues", I'm calling within the "node (Windows)" block, so I do not know where the /workspace prefix is coming from in this case. I will say that we are running multiple builds in parallel, some Linux and some Windows, so any chance information is leaking from one call of "recordIssues" to another call? The Linux builds (that use our /workspace overlay) finish long before the Windows builds, so I was wondering if that "/workspace" was leaking from one call to another. Since all of this is running within the Windows node, I'm not sure how anything from the master (which does nothing with /workspace) could influence the current "recordIssues" call. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-56001 NG Warnings plugin pre-pending '/workspace' before agent's workspace Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: warnings-ng 2.2.0 and analysis-model 2.1.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace I think I found the problem. Since your master is running Linux and the console log is scanned on the master, the path C:\something is not interpreted as absolute Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace Seems that the path is broken: /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp, it is composed of /workspace/TinyXml/ and C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp. How does this warning look in the original log? Are you building with make and have some make directory logging statements? make[2]: Entering directory '/dir1/dir2/dir3' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title
Shannon Kerr updated an issue
Jenkins / JENKINS-56001
NG Warnings plugin pre-pending '/workspace' before agent's workspace
Change By:
Shannon Kerr
(related to JENKINS-55998) We're moving from the legacy Warnings plugin to the NG plugin. For our Windows build executed on a Windows agent/slave, we're not getting to see the msbuild warnings in context on the build page. Our master is Linux and our pipeline agent node is also a Linux (Debian Stretch) node, but we execute some parallel builds on Windows agents.Here is some output from the NG Warnings info page:{code:java}Error MessagesCan't resolve absolute paths for some files:- /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp- /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/ptypes/src/pstring.cxx- /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/transport/source/AddrInfo.cpp ... skipped logging of 469 additional errors ...Can't create fingerprints for some files:- '/workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp', IO exception has been thrown: java.nio.file.NoSuchFileException: /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp{code} {code:java} Information MessagesParsing console log (workspace: '/var/lib/docker/exacqu/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ')Post processing issues on 'DockerAgent0' with encoding 'UTF-8'Resolving absolute file names for all issues-> 0 resolved, 489 unresolved, 0 already resolvedCopying affected files to Jenkins' build folder /var/jenkins_home/jobs/Server Branch/branches/build_updates/builds/167-> 0 copied, 0 not in workspace, 489 not-found, 0 with I/O errorResolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 9210 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 489 affected filesNo filter has been set, publishing all 9210 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issuesSkipping blaming as requested in the job configurationNo valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE)All reported issues will be considered outstandingNo quality gates have been set - skippingHealth report is disabled - skipping{code} Here is what our build block looks like:{code:java}node (build_mach) {bat '''@echo off'''recordIssues(tools: [msBuild(id: "msbuild-$os$arch", name: "MSBuild Compiler $target")])}{code} It does appear to capture all/only [?] the
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-56001 NG Warnings plugin pre-pending '/workspace' before agent's workspace Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-06 19:37 Environment: Jenkins 2.138.1 and NG Warnings plugin 2.1.2 Priority: Major Reporter: Shannon Kerr (related to JENKINS-55998) We're moving from the legacy Warnings plugin to the NG plugin. For our Windows build executed on a Windows agent/slave, we're not getting to see the msbuild warnings in context on the build page. Our master is Linux and our pipeline agent node is also a Linux (Debian Stretch) node, but we execute some parallel builds on Windows agents. Here is some output from the NG Warnings info page: Error Messages Can't resolve absolute paths for some files: - /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp - /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/ptypes/src/pstring.cxx - /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/transport/source/AddrInfo.cpp ... skipped logging of 469 additional errors ... Can't create fingerprints for some files: - '/workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp', IO exception has been thrown: java.nio.file.NoSuchFileException: /workspace/TinyXml/C:/DVR/workspace/_
