Documentation improvement about nuke

[matkoch]

Tracked here with https://github.com/nuke-build/web/pull/2. If you like, you can take a look at it.

[matkoch]

@dnknitro did you have a chance to take a look? Anything missing from your point of view?

[dnknitro]

Yeah, I looked through the whole page. I remember when I was trying nuke.build for the first time I had issues with actually invoking commands like OpenCover, MS Test etc. because all of those lacked executable tool path. So I had to figure out how to get that path and setup nuke.build target appropriately so it works both locally and on the build server.

I have not tried to follow this new wiki page with instructions though, just read it.

[matkoch]

@dnknitro I had a look at your repositories previously already. The way you do it shouldn't be necessary. Nuke should determine the tool path automatically for most tools. Sometimes you need to add them as a package reference though. VsTest and SignTool are one of the few exceptions, where you have to set it yourself.

If you like, you can join our slack or gitter channel to have a chat about that.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.