-
Improvement
-
Resolution: Unresolved
-
Minor
-
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
Jon B
created issue -
Jon B
made changes -
| Description |
Original:
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? |
New:
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? |
| Component/s | New: pipeline [ 21692 ] | |
| Component/s | Original: core [ 15593 ] |
| Component/s | New: workflow-job-plugin [ 21716 ] | |
| Component/s | Original: pipeline [ 21692 ] |