Hi.
I more often than seldom seem to need to upgrade ncrunch grid nodes to the same version I use for vstudio2015. Wasn't the idea to minimize this so the grid nodes can continue working with their old version towards a newer vstudio NCrunch version?
Maybe you can write some note in the changelist which grid node version is compatible with the newer vstudio version, so one can decide if it is worth upgrading "now" or wait until there's time to do it for the grid nodes as well to avoid them being outdated?
Thanks.
Remco NCrunch Developer
#8028
19 Nov 2015 22:12 UTC
GreenMoose wrote:
I more often than seldom seem to need to upgrade ncrunch grid nodes to the same version I use for vstudio2015. Wasn't the idea to minimize this so the grid nodes can continue working with their old version towards a newer vstudio NCrunch version?
Yes, sorry. The changes in recent versions have often required changes to the protocol, so it hasn't really been possible to avoid this. You've been likely hit by this particularly badly as I understand you've been installing quite a few dev builds (each with their own breaking changes).
GreenMoose wrote:
Maybe you can write some note in the changelist which grid node version is compatible with the newer vstudio version, so one can decide if it is worth upgrading "now" or wait until there's time to do it for the grid nodes as well to avoid them being outdated?
This is sensible. I'll make a note in the release plan to see that this gets added to the notes for each release. Thanks.
Post a reply
Log in to reply.