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

Task plugin logs each time it doesn't have to do anything

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • tasks-plugin
    • None
    • Task Scanner Plugin 4.24

      The plugin logs - for my taste - a little bit too verbose that it doesn't have do anything:

      10:10:49 [INFO] [clean:clean

      {execution: default-clean}

      ]
      10:10:49 [INFO] Deleting xyz
      10:15:37 [TASKS] Scanning folder 'xyz' for files matching the pattern '*/.java'
      [TASKS] Found 0 files to scan for tasks 10:15:37 Found 0 open tasks.
      10:15:37 [TASKS] Using set difference to compute new warnings 10:15:37 [TASKS] Not changing build status, since no threshold has been exceeded
      10:15:37[INFO] Preparing source:jar
      10:15:39 [INFO] [buildnumber:create

      {execution: default-execution-id}

      ]
      ...
      10:15:39 [TASKS] Skipping maven reporter: there is already a result available.
      10:15:40 [JENKINS] Archiving disabled - not archiving xyz
      10:15:40 [INFO] [source:jar

      {execution: default-cli}

      ]
      10:15:40 [TASKS] Skipping maven reporter: there is already a result available.
      10:15:40 [INFO] [architecture-rules:check-rules

      {execution: default}

      ]
      10:15:40 [TASKS] Skipping maven reporter: there is already a result available.
      10:15:40 [INFO] [buildnumber:create

      {execution: default-execution-id}

      ]
      10:15:40 [TASKS] Skipping maven reporter: there is already a result available.
      10:15:40 [debug] execute contextualize

      I.e. it seems to log for each mojo execution - after the 1st - on each module that it doesn't have to do anything anymore.
      Could you remove these please as they IMHO only unnecessary inflate the build console?

            drulli Ulli Hafner
            kutzi kutzi
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: