Agent creates a hidden $TF folder at random in one of all mapped folders

[jesfer]

Agent creates a hidden $TF folder at random in one of all mapped folders

See screenshots below. Depending on how I structure the local folders the $TF folder will appear in a different folder. Unpredictable behaviour and it has already messed up multiple build artifacts for us.

Agent version and platform

Agent Version: 2.112.0
OS: Windows Server 2008 R2 Standard
TFS: 2017.1 (15.112.26301.0)

(TFS and build server are separate machines)

Screenshots

[ericsciple]

@jesfer i think a root mapping folder would bring predictability

[jesfer]

@ericsciple A root mapping folder? Can you explain/give an example?

[ericsciple]

type: map
server path: $/
local path:

type: cloak:
server path: $/notThisFolder

type: map
server path: $/thisFolder
local path: thisFolder

type: map
server path: $/alsoThisFolder
local path: alsoThisFolder

If that would require too many cloaks, another thing that might be easier to define would be define your root as a single-level map (e.g. $/my/root/directory/*) and then it only pulls direct descendants under that location (likely empty folders?)

[jesfer]

After experimenting a bit I see that the appearance of the $tf folder is consistent with how a "complex" local workspace mapping works on my machine as well... So guess I'll have to live with that, even if it is annoying :)

Your mapping/cloaking suggestion works as long as there are only a few folders involved.

In my case this was easier:

Gives me a nice and predictable result. Was that what you meant by "define your root as a single level map" @ericsciple ?

[jesfer]

I am closing this issue as it really has nothing to do with the agent (it is just how local workspaces work) and I now have a way to get a consistent and predictable behaviour.

[bryanmacfarlane]

Thanks! @ericsciple - anything to document here in the agent troubleshooting or best practices section?

[ericsciple]

@jesfer actually this this problem came up in the context of build artifacts. Assuming you are on VSTS and use the Copy Files task (stage contents) and then the Publish Build Artifacts task (publish staging folder), then you can specify an exclude pattern, e.g. !**/$tf/**

reference doc for pattern syntax is here

[jesfer]

Yes, that would also work ☺

[maheswar]

Can we clock the $tf folder, If i clock i am getting following error

The path '$/Documentation/Files/$tf' contains a '$' at the beginning of a path component. Remove the '$' and try again.

Please help me to solve this issue.

[TingluoHuang]

$/Documentation/Files/$tf is not a valid TFSVC path, why you have a nested $tf folder?