I’m not sure this is a bug, but something’s changed. As a part of a much larger build script, I have a Team Foundation version history action.
I’m getting an error from tf.exe that it’s unable to determine the workspace.
In testing with tf.exe in a command prompt, I can repro this behavior by running the tool from a current directory that’s not mapped to a source control folder. The error occurs even through the command line doesn’t reference any local path. It’s of the form:
tf history $/Development/blah/blah/blah /recursive /stopafter:1 /noprompt /version:Wworkspace;owner
I suspect this is a tfs behavior change between tfs 2013 and tfs 2018, but I know I’m not going to get msft to make a change to help me
One thought: an option on the tf history command to set the current directory in which the command is run would probably do the trick. Is there a way to do this from the before script maybe?