Hi, On 31.01.19 17:31, Steven Foster wrote:
> There is no such extra information file. This looks a bit like an
> interrupt to me, is there a way I can reproduce how Jenkins sends
> interrupts so I can verify that?
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)
Simon
[1]
https://developercommunity.visualstudio.com/content/problem/301840/msbuild-not-terminating.html
[2] https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller
[3] https://gitlab.kitware.com/cmake/cmake/issues/18219
--
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/115f850e-abd8-f380-0157-9a6676f382c6%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
