• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Component/s: warnings-ng-plugin
• Labels:

  None
• Environment:

  Jenkins 2.222
  Warnings Next Generation 8.0.0

1. exception.txt

   4 kB

   2020-03-03 07:14

[JENKINS-61303] warnings-ng-plugin: Exception when creating relative paths

Bernd Rausch created issue - 2020-03-03 07:16

Ulli Hafner made changes - 2020-03-03 08:35

Link

New: This issue duplicates JENKINS-61295 [ JENKINS-61295 ]

Ulli Hafner made changes - 2020-03-03 08:35

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Bernd Rausch made changes - 2020-03-03 08:36

Description

Original: Since the update to Warnings Next Generation 8.0.0, all C# projects in our environment fail because of the following exception: [MSBuild] -> found 147 issues (skipped 1481 duplicates)[MSBuild] -> found 147 issues (skipped 1481 duplicates)ERROR: Build step failed with exceptionjava.lang.IllegalArgumentException: 'other' has different root at sun.nio.fs.WindowsPath.relativize(WindowsPath.java:392) at  The full stack trace is in the attachment. This seems to be a result of the following improvement: JENKINS-58538 - JENKINS-57556 - Replace absolute paths with relative paths for issues ([#358|https://github.com/jenkinsci/warnings-ng-plugin/pull/358]) [@uhafner|https://github.com/uhafner] Perhaps this jdk bug is also relevant: [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6226081]

New: Since the update to Warnings Next Generation 8.0.0, all C# projects in our environment fail because of the following exception: {{[MSBuild] -> found 147 issues (skipped 1481 duplicates)}}{{ERROR: Build step failed with exceptionjava.lang.IllegalArgumentException: 'other' has different root at sun.nio.fs.WindowsPath.relativize(WindowsPath.java:392) at }} The full stack trace is in the attachment. This seems to be a result of the following improvement: JENKINS-58538  -JENKINS-57556-  Replace absolute paths with relative paths for issues ([#358|https://github.com/jenkinsci/warnings-ng-plugin/pull/358]) [@uhafner|https://github.com/uhafner] Perhaps this jdk bug is also relevant: [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6226081]