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

Ugly "%n" logged at end of line after "Skipping warnings blame"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • analysis-core-plugin
    • None
    • Jenkins 2.89.2
      Static Analysis Utilities 1.93
      Warnings Plug-in 4.64
      Windows

      I got this in a build log:

      Skipping warnings blame since pipelines do not have an SCM link.%n
[WARNINGS] Computing warning deltas based on reference build #2

      There is a spurious "%n" at the end of the line. It, and another one, were apparently added in analysis-core-plugin commit 6f481f0537c3c3db09f30678ba8ef7c99a771db0. Note that AbstractBlamer#log calls String.format to expand the "%n" syntax but BlameFactory#log logs the string as is.

          [JENKINS-48904] Ugly "%n" logged at end of line after "Skipping warnings blame"

          Ulli Hafner added a comment -

          Fixed in branch 3.0 (See a437ab5601974efafdd94cabeeec90e3d52638f0). 

          Ulli Hafner added a comment - Fixed in branch 3.0 (See a437ab5601974efafdd94cabeeec90e3d52638f0). 

            drulli Ulli Hafner
            kon Kalle Niemitalo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: