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

Killing off a bad pipeline run automatically

    Details

    • Similar Issues:

      Description

      Let's assume someone accidentally turns the verbosity all the way up in their code and then later, when run in a Jenkins pipeline, it generates many GB of console output. I've seen this happen and my Jenkins master becomes unresponsive disappointing people waiting onĀ other jobs.

      Is there some way I can instruct the Jenkins master to automtaically term any pipeline which is inflight that generates > 200mb of console logs, for example?

        Attachments

          Activity

          piratejohnny Jon B created issue -
          piratejohnny Jon B made changes -
          Field Original Value New Value
          Description Let's assume someone accidentally turns the verbosity all the way up and it generates many GB of console output. I've seen this happen and my Jenkins master becomes unresponsive.

          Is there some way I can instruct the Jenkins master to automtaically term any pipeline which is inflight that generates > 200mb of console logs, for example?
          Let's assume someone accidentally turns the verbosity all the way up in their code and then later, when run in a Jenkins pipeline, it generates many GB of console output. I've seen this happen and my Jenkins master becomes unresponsive disappointing people waiting on other jobs.

          Is there some way I can instruct the Jenkins master to automtaically term any pipeline which is inflight that generates > 200mb of console logs, for example?
          oleg_nenashev Oleg Nenashev made changes -
          Component/s pipeline [ 21692 ]
          Component/s core [ 15593 ]
          Hide
          abayer Andrew Bayer added a comment -

          Not that I can think of - the timeout step will let you kill the run if it takes too long, but I don't think there's any way at this point to do that if the logs get too big or somesuch. Probably could be done via a plugin, though.

          Show
          abayer Andrew Bayer added a comment - Not that I can think of - the timeout step will let you kill the run if it takes too long, but I don't think there's any way at this point to do that if the logs get too big or somesuch. Probably could be done via a plugin, though.
          abayer Andrew Bayer made changes -
          Component/s workflow-job-plugin [ 21716 ]
          Component/s pipeline [ 21692 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              piratejohnny Jon B
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: