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?