You need to meet the following requirements: · Point the working path to drive D

Your network environment includes a Microsoft Visual Studio Team Foundation Server 2012 (TFS) server. A
single build machine is installed with one controller and two agents. The working directories are configured to
use the following working directory:
$(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionPath). Your system drive is running out of space and
some builds often fail with the following error:
“The specified path, file name, or both are too long. The fully qualified file name must be less than 260
characters, and the directory name must be less than 248 characters.” You need to meet the following
requirements:
· Point the working path to drive D.
· Construct a working directory that can be used todefine the shortest unique path for each build agent it is
used on.
What should you do?

Your network environment includes a Microsoft Visual Studio Team Foundation Server 2012 (TFS) server. A
single build machine is installed with one controller and two agents. The working directories are configured to
use the following working directory:
$(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionPath). Your system drive is running out of space and
some builds often fail with the following error:
“The specified path, file name, or both are too long. The fully qualified file name must be less than 260
characters, and the directory name must be less than 248 characters.” You need to meet the following
requirements:
· Point the working path to drive D.
· Construct a working directory that can be used todefine the shortest unique path for each build agent it is
used on.
What should you do?

A.
Set the Build Agent working directory path to D:\BId\$(BuildAqentld)\$(BuildDetinitionPath).

B.
Create a system variable named BuildDrive and setits value to D:\.

C.
Set the Build Service working directory path to D:\BId\$(BuildAqentld)\$(BuildDefinitionPath).

D.
Set the Team Foundation Build variable named $(BuildDrive) to the value D:\.



Leave a Reply 2

Your email address will not be published. Required fields are marked *