Closed mrdavidlaing closed 11 years ago
If we assume that these values are fixed to some relative paths and we don't need to call external server, I can set them default values.
Managed to set the pathers from $(BinariesRoot)
-> 42edc2b5318ce7afac214e0e0686f08dad936bfa
Can we hardcode AppMetricsTest_AccessKey
? or perhaps set it at in the TFS build definition screen?
Fixed. AccessKey can be assigned any value in this case, because by default it's not required on the server side.
The build on the internal City Index TFS build farm is failing in ContinuousIntegration/testAndCover.xml
with error:
I see that on the EC2 TFS2010 build server there are a set of environment variables set with these names.
Is there a way remove the dependancy on having these environment variables set on the build agent.
My specific problem is that CI TFS runs a cluster of 6 build agents, which the job running on whichever one is free. I'd prefer not to have to manually add this env setting to every (existing) TFS build agent (and every new one that gets added).
Is this possible?
Can we calculate these env variables from an existing variable like:
$(MSBuildProjectDirectory)