-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
Windows 7 Pro 64 bit
MSBuild 15
Jenkins 2.150.3 (self-updated after install from the official 2.150.1 windows installer)
MSBuild-plugin 1.29
When using multiple (logical) cores for the build (/M switch), msbuild.exe spawns extra msbuild.exe processes (depending on the number of cores and build tasks). These spawned worker processes do not (immediately) shut down after build is finished, but they are re-used by subsequent invocations of msbuild.exe, so that's not a problem.
What is a problem though, is that the plugin hangs around for these worker processes to exit (I suppose), and with the 2 minute process termination waiting period introduced in 2.141, causes the build to stall for a period of a multiple of 2 minutes. As far as I can see, these worker processes are not a problem, and thus should not be forced to shut down. Setting -DSoftKillWaitSeconds=0 affects other things than this plugin, so I don't think that's a viable workaround.
[JENKINS-56234] Building on multiple cores causes plugin to stall
Tilo
added a comment - I'll add this information to our documentation and then close the issue. Does that work for you?
Tilo
added a comment - I'll add this information to our documentation and then close the issue. Does that work for you? Given it's been over 5 years, I'm not expecting anything, so do what you find best..
Thank you!
Tilo
added a comment - I'm the new maintainer of this project and am cleaning up some issues. Given it's been over 5 years, I'll handle it as best as I can.
Tilo
added a comment - I'm the new maintainer of this project and am cleaning up some issues. Given it's been over 5 years, I'll handle it as best as I can. 
I found out that by using the option /nr:false (node reuse=false), the spawned build processes are terminated as soon as the parent is done, and so fixes the stall. Since the plugin insists on waiting for the spawned processes to end, this option should probably be implicit.