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

Killing off a bad pipeline run automatically

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • workflow-job-plugin
    • None

      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?

          [JENKINS-51184] Killing off a bad pipeline run automatically

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

              Created:
              Updated: