On Thursday, January 31, 2019 at 4:45:40 PM UTC, Simon Richter wrote: > > > There are a few things going on: > > - MSBuild sticks around after a build if the same project is rebuilt > - Jenkins kills processes belonging to a build after it believes the > build has finished > - MSBuild has serious issues with memory management > > All of these are somewhat unpredictable. > > I've found that it becomes a bit better if you set an environment variable > > MSBUILDDISABLENODEREUSE=1 > > as suggested[1] by the VS team, disable the Jenkins Process Tree > Killer[2] and try to use the 64 bit version of MSBuild[3] to avoid > running out of virtual memory (which MSBuild sometimes, but not always > reports as the reason for termination in the log files in %APPDATA%\Temp) >
Thanks for the leads, I will look into those. Just to note that the issue only appeared after updating Jenkins (identical build agent images) and the builds were running fine before. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e7a25c32-ed5d-489b-8f63-f87902b12e57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
