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

Empty console when properties compressBuildLog() is enabled

XMLWordPrintable

      Had Pipeline Job Plugin 2.25.

      Our jobs have properties([...., compressBuildLog(), ...]) enabled.

      Upgrade to 2.31 along with a lot of dependencies.

      With the new plugin, the build console shows the output as long as the build is running. When the build is finished, there is no console anymore for a build (neither default /job/<jobname>/job/<branchname>/<buildnumber>/console nor .../consoleFull or .../consoleText ).

      Remove compressBuildLog() from properties, run a build --> issue is gone for the new build. Of course, for the builds which had compressed build logs, the issue persists.

      Looks like the new console view does not work with compressed build logs.

      Setting to Critical as this should be mentioned at least in the upgrade notes. I don't have a chance from Classic Jenkins UI to view the logs anymore.

          [JENKINS-55465] Empty console when properties compressBuildLog() is enabled

          Devin Nusbaum added a comment -

          Are there any related error messages in your Jenkins logs?

          It looks like the compressBuildLog property comes from Compress Build Log Plugin, but based on the description on that page I think the decompression side of things is handled somewhere in a core API.

          It is certainly possible that this functionality is broken in workflow-job 2.26+, although I am not sure why or what would be required to get it working again. Note also that in workflow-job 2.26+, log data is no longer duplicated in individual step logs, so your logs should automatically take 50% less space, so turning off compression might be a good short term solution.

          Devin Nusbaum added a comment - Are there any related error messages in your Jenkins logs? It looks like the compressBuildLog property comes from  Compress Build Log Plugin , but based on the description on that page I think the decompression side of things is handled somewhere in a core API. It is certainly possible that this functionality is broken in workflow-job 2.26+, although I am not sure why or what would be required to get it working again. Note also that in workflow-job 2.26+, log data is no longer duplicated in individual step logs, so your logs should automatically take 50% less space, so turning off compression might be a good short term solution.

            Unassigned Unassigned
            beyerj Jens Beyer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: