Automatic tool detection with Jenkins/Hudson?
*What mechanisms exists in Jenkins/Hudson to automatically detect tools that are installed on the Nodes?*

For example, .NET frameworks, Visual Studio versions, Setup-Builder Tools, installed scripting language executables, etc.

I'm currently trying to figure out if and how (and whether it makes sense) Jenkins can auto-detect our tools that I have to install on all the Nodes (Salves).

Since our Nodes are Windows machines, hard-coding paths doesn't make sense (IMHO) due to path mismatch Windows 64bit vs. 32bit / XP vs. Windows 7 / different language versions.

Also, quite a few tools require installation, so just mirroring over files isn't an option either.

<sub>Obviously, I could just define a set of environment variables for our tools and use these from Jenkins. But I much rather use/build something that makes new Nodes/Slaves auto-configured.</sub>
Automatic tool detection with Jenkins/Hudson?
===

*What mechanisms exists in Jenkins/Hudson to automatically detect tools that are installed on the Nodes?*

For example, .NET frameworks, Visual Studio versions, Setup-Builder Tools, installed scripting language executables, etc.

I'm currently trying to figure out if and how (and whether it makes sense) Jenkins can auto-detect our tools that I have to install on all the Nodes (Salves).

Since our Nodes are Windows machines, hard-coding paths doesn't make sense (IMHO) due to path mismatch Windows 64bit vs. 32bit / XP vs. Windows 7 / different language versions.

Also, quite a few tools require installation, so just mirroring over files isn't an option either.

<sub>Obviously, I could just define a set of environment variables for our tools and use these from Jenkins. But I much rather use/build something that makes new Nodes/Slaves auto-configured.</sub>