@lacostej When building the mainline I had to modify the jenkins/war/pom.xml file in the to this:
<resolveArtifact groupId="org.jvnet.hudson" artifactId="executable-war" version="1.17" type="jar" property="executable-war.jar" />
instead of trying to pull version 1.18-SNAPSHOT, which doesn't exist. Also, it doesn't appear that a Jenkins build has run on ci.jenkins-ci.org for a few days. Is that common when preparing for a release or is it just because of the infrastructure transition? I tried to kick one off but remote-slave-2 (which I guess jenkins_main_trunk is tied to) is offline.
Anyway, testing with the same configuration as earlier: OS X 10.6.6 Master to Vista Slave, copying a 74MB file from an upstream project to the remote machine, downloading another file from the slave, and running every minute I ended up with the following results: 120 builds, no failures. As best I can tell from this testing the issue appears to be fixed. As of right now it looks like you won't need my patch after all. That's fine with me, I'll contribute some code eventually .