This pattern of switching from pull to push is something the remoting library should support. This change is added to https://github.com/jenkinsci/remoting/commit/42ed097929beac8b588d90e7df092847e10c0a67 and several following commits.

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/src/main/java/hudson/FilePath.java
core/src/main/java/hudson/Launcher.java
core/src/main/java/hudson/cli/ClientAuthenticationCache.java
core/src/main/java/hudson/os/SU.java
core/src/main/java/hudson/slaves/SlaveComputer.java
core/src/main/java/hudson/util/ProcessTree.java
core/src/main/java/jenkins/model/Jenkins.java
core/src/test/java/hudson/LauncherTest.java
http://jenkins-ci.org/commit/jenkins/0b27f364f99ec98cb616d4f0cfc0858ecf339852
Log:
JENKINS-22354

Avoid having FilePath to depend on Jenkins, which increases the amount of classloading that has to happen during remoting

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/src/main/java/hudson/model/Result.java
http://jenkins-ci.org/commit/jenkins/8a530bb14b4325ff1a75ce89b63b53b7271a6702
Log:
JENKINS-22354

Reduce classloader activities.

This brings in Stapler and commons bean-utils that we don't need on the
slaves.

Compare: https://github.com/jenkinsci/jenkins/compare/dcfeaf3c2a12...8a530bb14b43

Integrated in jenkins_main_trunk #3280
JENKINS-22354 (Revision 0b27f364f99ec98cb616d4f0cfc0858ecf339852)
JENKINS-22354 (Revision 8a530bb14b4325ff1a75ce89b63b53b7271a6702)

Result = UNSTABLE
kohsuke : 0b27f364f99ec98cb616d4f0cfc0858ecf339852
Files :

• core/src/main/java/jenkins/model/Jenkins.java
• core/src/main/java/hudson/FilePath.java
• core/src/main/java/hudson/cli/ClientAuthenticationCache.java
• core/src/main/java/hudson/slaves/SlaveComputer.java
• core/src/test/java/hudson/LauncherTest.java
• core/src/main/java/hudson/util/ProcessTree.java
• core/src/main/java/hudson/os/SU.java
• core/src/main/java/hudson/Launcher.java

kohsuke : 8a530bb14b4325ff1a75ce89b63b53b7271a6702
Files :

• core/src/main/java/hudson/model/Result.java

Hi Kohsuke,

any updates to this issue? We have a large project where we want all 24 cores of our machine to build on but it get always stuck with that race condition at SplittableBuildListener. The only "solution" is to disable parallel maven builds.

Thanks in advance!

Max

maxzilla: It's not resolved in Maven plugin 2.2? The commit seems to indicate that the issue is fixed.

No, unfortunately it doesn't seem to fix it. We use Jenkins 1.562 and Maven plugin 2.3, so the fix should be deployed. Is there anything I have to keep in mind for the slave's configuration? We restarted the master and the slaves but issue still exists.

Yeah, this is still the case in Maven plugin 2.4-SNAPSHOT as of today - I opened JENKINS-23340 but then found this.

JENKINS-23098 is fixed. So is there more to do here?

No replies - closing.