|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
It was reported as a specific issue, just in case it's possible to fix this one issue without fixing the whole core of Jenkins. Well over 90% of our "build failures" (actually Jenkins-fails, not build failures) happen during the copying of files in one direction or the other, so even fixing this one issue would improve things enormously. (Hell will probably freeze over before Jenkins devs start to care about reliability of the architecture itself. Many years have passed with no improvements in that area whatsoever, so I have no reason to start believing in it at this point in time.)
If there are any plugins which can tolerate disconnects during job execution, they appear to be missing from the list. https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Slavelaunchersandcontrollers