Details
-
Bug
-
Resolution: Fixed
-
Major
Description
Since yesterday we've installed the logfilesizechecker-plugin on our Jenkins (2.138.3) and the Jenkins Log is flooded with the following Exception
Avoid calling getLogFile on sanmx-tm/feature%-1-payment #1 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at hudson.plugins.logfilesizechecker.LogfilesizecheckerWrapper$LogSizeTimerTask.doRun(LogfilesizecheckerWrapper.java:108) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
The Exception is written in the log, as the method getLogFile() is deprecated.
https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile--
@Deprecated
@Override public File getLogFile() {
LOGGER.log(Level.WARNING, "Avoid calling getLogFile on " + this, new UnsupportedOperationException());
return LogStorage.of(asFlowExecutionOwner()).getLogFile(this, !isLogUpdated());
}
Our filesystem on the master went out of space, as due to our amount of Jobs and the Timersettings in the plugin the code is called very often.
We've installed the plugin to prevent that builds are flooding the filesystem with logs and now the plugin itself does the flooding. Thats bad humor 
Attachments
Issue Links
- is related to
-
-
- Open
-