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

Programs with user prompts fill jenkins log until disk runs out of space

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: core
    • Labels:
    • Environment:
      Linux - centos 5
    • Similar Issues:

      Description

      If there is a user prompt in the build, that is a program that allows the user to select options or generally waits for user input, then the prompt text will repeat indefinitely within the jenkins build log until the log uses up all available disk space.

      I encounter this error when automating the building of the linux rootfs package (root file system, or all the open source packages in our embedded software platform). If anyone has used the 'make oldconfig' to compile linux I believe the experience is similar, it produces a little menu allowing you to select which package you would like to use for compilation. This menu will repeat constantly and simply fill up the log until there isn't any room left on the disk.

      I think there are a couple routes to try and solve this:
      1) Fail the job when user input is needed. Although this might be impossible to detect.
      2) Not repeat the prompt and simply sit there, waiting for user input that will never come. Harder for the user to notice that there is something wrong with the job, but at least it doesn't kill the disk.
      3) If neither of the above will work then maybe just add log protections, as in if the log grows too large and disk space is about to run out, fail the build.

      Not sure what components this should be listed under, sorry if I guessed the wrong ones.

        Attachments

          Activity

          Hide
          centic centic added a comment -

          remove component "disk-usage" as this is not related to the "disk usage plugin"

          Show
          centic centic added a comment - remove component "disk-usage" as this is not related to the "disk usage plugin"
          Hide
          danielbeck Daniel Beck added a comment -

          Not a Jenkins bug, but a bug in the build script or the tools being called that should be able to determine that they're not writing their output to an interactive shell. From Jenkins, what happens should be indistinguishable from a well-behaving build.

          Aborting running builds before space runs out seems pointless, because on a Jenkins server, builds getting aborting because space has run out appears to be the most severe result.

          Plugins like Logfilesizechecker and build-timeout plugin do the job wrt automatically determinable misbehaving builds.

          Show
          danielbeck Daniel Beck added a comment - Not a Jenkins bug, but a bug in the build script or the tools being called that should be able to determine that they're not writing their output to an interactive shell. From Jenkins, what happens should be indistinguishable from a well-behaving build. Aborting running builds before space runs out seems pointless, because on a Jenkins server, builds getting aborting because space has run out appears to be the most severe result. Plugins like Logfilesizechecker and build-timeout plugin do the job wrt automatically determinable misbehaving builds.

            People

            • Assignee:
              vjuranek vjuranek
              Reporter:
              devin_linnington Devin Linnington
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: