Newtwork operations in copyartifact-plugin depends on FilePath provided by Jenkins core (I added core to components).

Though I'm not sure how Jenkins core manages network connections between a master and slaves, I suppose that a file transfer hangup means disconnection between the master and the slave, and Jenkins can no longer continue the job.

Anyway, let us know how to reproduce the problem if you know.
Or, please get threaddumps (both for the master and the slave) if you face the same problem again.
That will be a great help for us to see what happens internally.

Change By: ikedam (20/Nov/14 1:01 AM)
Summary: Archiving artifacts  (or FilePath operatons)  should properly time out and retry the copy
Component/s: core
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to