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

WARNINGs are filling the log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: delivery-pipeline-plugin, token-macro-plugin
    • Labels:
      None
    • Environment:
      Jenkins version: 2.32.1
      Java version: 1.7.0_91
      Delivery pipeline plugin version: 0.10.1
      Token Macro plugin version: 2.0
      OS: CentOS 6.7
    • Similar Issues:

      Description

      Upgrading the Token Macro plugin to version 2.0 leads to filling Jenkins logs with the following messages:

      Dec 27, 2016 2:59:30 PM WARNING se.diabol.jenkins.pipeline.token.TokenUtils decodedTemplate
      Workspace is not accessible

      Most of jobs are configured to run on slaves which comes up only by necessity.

        Attachments

          Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-41672 Tune log level for macro evaluation exceptions in TokenUtils

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            sailingareus Christopher Williams added a comment - - edited

            I have a similar issue but even worse. Delivery pipeline plugin version: 0.10.2 Where LOG.log(Level.WARNING, "Failed to evaluate token using token-macro plugin", e) in src/main/java/se/diabol/jenkins/pipeline/token/TokenUtils.java flooded (JENKINS-40763) our stdout with stack-traces in our docker container that runs a Jenkins master. This brought it down because all stdout in a docker container is stored to disk and caused us to run out of disk (450GB). Thank goodness for Logrotate

            Hälsar
            Chris

            Show
            sailingareus Christopher Williams added a comment - - edited I have a similar issue but even worse. Delivery pipeline plugin version: 0.10.2 Where LOG.log(Level.WARNING, "Failed to evaluate token using token-macro plugin", e) in src/main/java/se/diabol/jenkins/pipeline/token/TokenUtils.java flooded ( JENKINS-40763 ) our stdout with stack-traces in our docker container that runs a Jenkins master. This brought it down because all stdout in a docker container is stored to disk and caused us to run out of disk (450GB). Thank goodness for Logrotate Hälsar Chris
            Hide
            Permalink
            tommysdk Tommy Tynjä added a comment -

            This should have been resolved by JENKINS-41672 released in 0.10.3. Otherwise, please let me know.

            Show
            tommysdk Tommy Tynjä added a comment - This should have been resolved by JENKINS-41672 released in 0.10.3. Otherwise, please let me know.

              People

              Assignee:
              tommysdk Tommy Tynjä
              Reporter:
              ivan_ivanou Ivan Ivanou
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: