Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56001

NG Warnings plugin pre-pending '/workspace' before agent's workspace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-ng-plugin
    • None
    • Jenkins 2.138.1 and NG Warnings plugin 2.1.2
    • warnings-ng 2.2.0 and analysis-model 2.1.1

      (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/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp
      

       

      Information Messages
      
      Parsing 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 resolved
      Copying 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 error
      Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
      -> resolved module names for 9210 issues
      Resolving package names (or namespaces) by parsing the affected files
      -> resolved package names of 489 affected files
      No filter has been set, publishing all 9210 issues
      Creating fingerprints for all affected code blocks to track issues over different builds
      -> created fingerprints for 0 issues
      Skipping blaming as requested in the job configuration
      No valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE)
      All reported issues will be considered outstanding
      No quality gates have been set - skipping
      Health report is disabled - skipping
      

      Here is what our build block looks like:

      node (build_mach) {
          bat '''
              @echo off
              <build here>
          '''
          recordIssues(tools: [msBuild(id: "msbuild-$os$arch", name: "MSBuild Compiler $target")])
      }
      

       

      It does appear to capture all/only [?] the issues for each Windows build (we have 2 that run in parallel for x86 and x64), we are unable to see any issues in the source context.

            drulli Ulli Hafner
            kerrhome Shannon Kerr
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: