Where is autodetected path to MSTest.exe saved?

Hi, the documentation says that the path to MSTest.exe is autodetected by the build agent. Now, I would expect to find the property "system.MSTest.10.0", for example, defined in buildAgent.properties. But I don't see this property. The teamcity-agent.log says:

[2015-01-21 06:15:44,316]   INFO - cher.DotNetPropertiesExtension - Start MSTest Searcher
[2015-01-21 06:15:44,754]   INFO - cher.DotNetPropertiesExtension - Found MSTest 10.0
[2015-01-21 06:15:44,754]   INFO - cher.DotNetPropertiesExtension - Finished MSTest Searcher


Where is autodetected path to MSTest.exe saved?

Thanks in advance.
4 comments
Comment actions Permalink

Hi Markus,

buildAgent.properties file contain agent-specific properties, which you could manually add to this file. While system property "system.MSTest.10.0"  is passed into the build scripts. You can use %system.MSTest.10.0% inside your build script and it will be substituted with the actual value at the time of build.

0
Comment actions Permalink

Thank you for your answer. I do not have set "system.MSTest.10.0" in my buildAgent.properties file. Where is the system property "system.MSTest.10.0" defined? Or is it undefined, if I do not set it in my buildAgent.properties file? I did a search on all *.properties files in the agent home directory, but none has property "system.MSTest.10.0" set. I was thinking that the actual value of this system property should be determined on the agent machine and thus be saved somewhere on the agent machine.

0
Comment actions Permalink

When agent starts it searches for necessary build tools it needs, such as MSTest, JDK, .net framework, etc. For every tool it finds it reports a property with tool name and its version. These properties are not saved anywhere. They are runtime and used by server to determine if the particular agent can run a build that requires, for instance, MSTest 10 and .NET Framework 4.5

0
Comment actions Permalink

Thanks for clarification!

spak schrieb:

These properties are not saved anywhere. They are runtime and used by server to determine if the particular agent can run a build that requires, for instance, MSTest 10 and .NET Framework 4.5

0

Please sign in to leave a comment.