-
New Feature
-
Resolution: Unresolved
-
Major
-
None
- relates to
-
JENKINS-52165 Use push rather than pull for durable task logging
-
- Reopened
-
JENKINS-52165
Use push rather than pull for durable task logging
Worth testing behavior in conjunction with JENKINS-52165. If I have a long-running sh step and at some point in the middle the agent JVM crashes, what happens? With a typical JNLP agent service, the expectation (either before or after the changes in JENKINS-52165) is that a new JVM reconnects at some point, using the same agent name, and the Jenkins master resumes streaming log content from the step, and whenever it finishes the build proceeds.