You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MSBuildDefaults <- { MSBuildDefaults with NodeReuse = false}
is the way to go on TeamCity, as for example the stylecop.dll's will be locked for, I think, 60 seconds if nodereuse is on. This causing clean to fail if the next build comes within 60 seconds of the previous completing. This caused issues for us and we have been running with node-reuse off in all our build scripts for months now.
The text was updated successfully, but these errors were encountered:
As commented on http://theimowski.com/blog/2016/01-18-continuous-delivery-with-fake-paket-and-teamcity/index.html I think running with
is the way to go on TeamCity, as for example the stylecop.dll's will be locked for, I think, 60 seconds if nodereuse is on. This causing clean to fail if the next build comes within 60 seconds of the previous completing. This caused issues for us and we have been running with node-reuse off in all our build scripts for months now.
The text was updated successfully, but these errors were encountered: