• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Jenkins 2.138.3
      Pipeline Multibranch with defaults 2.0
      Pipeline Multibranch Plugin 2.20
      Build Pipeline Plugin 1.58

      The logs in /job/master/167/console are shown when the build is in progress.
      After it has finished I see nothing. Only a black narrow bar.
      The BlueOcen shows me this stacktrace

      java.io.FileNotFoundException: /var/lib/jenkins/jobs/Invoice/branches/master/builds/166/log (No such file or directory)
      
      	at java.io.RandomAccessFile.open0(Native Method)
      
      	at java.io.RandomAccessFile.open(RandomAccessFile.java:316)
      
      	at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243)
      
      	at org.jenkinsci.plugins.workflow.log.FileLogStorage.stepLog(FileLogStorage.java:259)
      
      	at org.jenkinsci.plugins.workflow.support.actions.LogStorageAction.getLogText(LogStorageAction.java:62)
      
      	at io.jenkins.blueocean.rest.impl.pipeline.PipelineStepImpl.getLog(PipelineStepImpl.java:139)
      
      	at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
      
      

          [JENKINS-54678] Compression trick not supported by JEP-210

          Tibor Digana created issue -

          Same problem spotted on 2.138.2

          Thomas Vuillaume added a comment - Same problem spotted on 2.138.2

          Tibor Digana added a comment -

          jglick
          Who should handle this issue?
          I am doing an internal workshop in my company about Jenkins on December 3rd and this issue is a big problem.

          Tibor Digana added a comment - jglick Who should handle this issue? I am doing an internal workshop in my company about Jenkins on December 3rd and this issue is a big problem.
          Thomas Vuillaume made changes -
          Attachment New: standardModulePipeline.groovy [ 45261 ]

          Thomas Vuillaume added a comment - - edited

          I'm sharing my Pipeline file so that we can move on (and maybe found a root cause).

           

          Anyway, this is pretty strange because we have 2 different Jenkins here. Both of them are on 2.138.2, both of them use Pipeline Build 1.5.8. Both of them use a pipeline to build, but not the same pipeline.

           

          Only one faces the issue (the one which uses the pipeline I added to this ticket)

          Thomas Vuillaume added a comment - - edited I'm sharing my Pipeline file so that we can move on (and maybe found a root cause).   Anyway, this is pretty strange because we have 2 different Jenkins here. Both of them are on 2.138.2, both of them use Pipeline Build 1.5.8. Both of them use a pipeline to build, but not the same pipeline.   Only one faces the issue (the one which uses the pipeline I added to this ticket)

          Jesse Glick added a comment -

          I presume

          compressBuildLog()
          

          is to blame. Try deleting that and uninstalling this plugin. Its Pipeline compatibility should be removed, as it will not work as of workflow-job 2.26.

          Jesse Glick added a comment - I presume compressBuildLog() is to blame. Try deleting that and uninstalling this plugin. Its Pipeline compatibility should be removed, as it will not work as of workflow-job 2.26.
          Jesse Glick made changes -
          Component/s New: compress-build-log-plugin [ 20220 ]
          Component/s Original: pipeline [ 21692 ]
          Labels New: pipeline

          Confirmed !

           

          Thanks jglick, this did work ! I removed the compressBuildLog() and uninstalled the pluggin.

          I guess tibor17 will be pleased to have been saved before the 3rd of December !

          Many thanks !

          Thomas Vuillaume added a comment - Confirmed !   Thanks jglick , this did work ! I removed the compressBuildLog() and uninstalled the pluggin. I guess tibor17 will be pleased to have been saved before the 3rd of December ! Many thanks !

          Jesse Glick added a comment -

          Note that JEP-210 defines a beta, but supported, API for properly replacing build log storage as a whole, which theoretically this plugin could implement via log.gz. (Run.getLogFile is slated to be deprecated and is not supported by new versions of Pipeline.) That said, if you are compressing build logs because you are concerned about storage space on the master, the way forward is likely to be cloud log storage, as in the recently released pipeline-cloudwatch-logs plugin.

          Jesse Glick added a comment - Note that JEP-210 defines a beta, but supported, API for properly replacing build log storage as a whole, which theoretically this plugin could implement via log.gz . ( Run.getLogFile is slated to be deprecated and is not supported by new versions of Pipeline.) That said, if you are compressing build logs because you are concerned about storage space on the master, the way forward is likely to be cloud log storage, as in the recently released pipeline-cloudwatch-logs plugin.
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-54680 [ JENKINS-54680 ]

            Unassigned Unassigned
            tibor17 Tibor Digana
            Votes:
            34 Vote for this issue
            Watchers:
            39 Start watching this issue

              Created:
              Updated: