[JIRA] (JENKINS-59781) sshCommand fails to flush full log on failure

[christian.ci...@gmail.com (JIRA)]

Title: Message Title

Christian Ciach edited a comment on JENKINS-59781   Re: sshCommand fails to flush full log on failure This issue does not only apply to failures, but all logging of this plugin (even its own status logging, like "{{Executing command on name[server]: mycommand sudo: false"}}). Looking at the code, it seems to me that the likely issue is a missing flush()-call to the CustomLogHandler (or maybe the rootLogger) at the end of this method: [https://github.com/jenkinsci/ssh-steps-plugin/blob/c35e7db86e975b257343179fd4f08dd0af8cbb42/src/main/groovy/org/jenkinsci/plugins/sshsteps/SSHService.groovy#L55] That being said.. Is it really a good Idea to register a new CustomLogHandler every time something gets logged? The rootLogger is most likely static, so adding new handlers for each and every message will eventually lead to a ton of CustomLogHandlers that are probably never garbage collected. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202509.1571085160000.3582.1585659067589%40Atlassian.JIRA.