MSBuild Task - Store Log file outside Source Folder

When launching an MSBuild task, the command line look like

C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe 
"C:\vso_agent\_work\2\s\MSBuild.targets" /nologo /m /nr:false /fl /flp:"logfile=C:\vso_agent\_work\2\s\MSBuild.targets.log"
/dl:CentralLogger,"C:\vso_agent\agent\worker\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll"*ForwardingLogger,"C:\vso_agent\agent\worker\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll"

This part /flp:“logfile=C:\vso_agent_work\2\s\MSBuild.targets.log” creates a log file inside the source folder. The first instruction of our build script is a git clean and because this file is locked, we have to explicitly skip it to have the git clean work. It could be nice to have this file created outside the source folder. I am not sure this is the right place to post this issue as I’m not sure the code related to that is inside this project. If not, please, tell me where to submit this request.

Thank you

[ericsciple]

Fixed when this commit rolls out: https://github.com/Microsoft/vsts-tasks/commit/97f83b21d5330cddf4d43bbeaf440602f10ba670

Next deployment starting in a couple days.

[ericsciple]

@chrisrpatterson - the request here is to put the msbuild log somewhere else. The customer is calling git clean -fdx from within their msbuild targets and the log file is in use.

It sounds like there is multiple workarounds. E.g. clean on the repo tab now does git clean fdx (and then reset hard). However, I still wonder if we get in the way if a customer’s normal dev process (i.e. build from dev box) is to have git clean fdx within the targets file.

It might be good to change this as part of the agent.tempdirectory idea we keep finding more potential uses for.