[JIRA] (JENKINS-50379) Jenkins kills long running sh script with no output

[jacob.kel...@gmail.com (JIRA)]

Title: Message Title

Jacob Keller commented on JENKINS-50379   Re: Jenkins kills long running sh script with no output > The problem is not that your script stops producing output for a while. That is perfectly normal and supported. The problem is that a side process which is supposed to be detecting this fact and touching the log file every three seconds is either not running, or not producing the right timestamp as observed by the Jenkins agent JVM. Right, so it sounds like we need to investigate why the side process that should be touching the log file isn't working properly. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.189432.1521834811000.848.1568144400672%40Atlassian.JIRA.