Ant Task in Team Foundation Server Build Extensions Power Tool not working

Question

In the TFS Build Extensions Power Tool, I am trying to use the Ant task.  I simply included the new tasks file, instead of the old Teamprise one, and am now getting the following error:

warning MSB4018: The "Ant" task failed unexpectedly.

warning MSB4018: System.ArgumentNullException: Value cannot be null.

warning MSB4018: Parameter name: rootTracking

warning MSB4018:    at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)

warning MSB4018:    at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)

warning MSB4018:    at Microsoft.TeamFoundation.Build.Extensions.Tasks.WorkflowTask.Execute()

warning MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()

warning MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)

Answer 1

I'm looking into this one right now.  Looks to be a common issue with both the Ant and Maven integration.  We've also started getting intermittent repros of this with our own CI build of Team Explorer Everywhere locally (we use the power tools to build Team Explorer Everywhere)

Anyway - hope to get back to you soon with a resolution.  If it requires a new version of the power tools then we'll try and get the fix into the next release.

I will let you know how we get on.

Martin.

 

---

http://www.woodwardweb.com

Answer 2

The only way I could "solve" this was by moving over to the new WF Team Build System and using the Ant Activity, instead of the Task.

Answer 3

how do You know when you are using a Workflow Ant activity instead of a task?

 

Answer 4

how do You know when you are using a Workflow Ant activity instead of a task?

 

You have to convert your build process to use the new Team Build process in WF, then link in the Activity.  Trust me, if you've converted over to the new WF-based system, you'll know.  :)

Answer 5

FYI, Found the workaround @ the link below, my build server has multiple agents configured (which seems to induce the root cause), just needed to identify which agent executed the build successfully (Agent 1 in my case) Added a tag to the agent and modified the build definition to point to that agent.

http://social.msdn.microsoft.com/Forums/en/tee/thread/2ed2209b-7e60-4f72-863e-dd88d09ae115

 

 

Answer 6

FYI, Found the workaround @ the link below, my build server has multiple agents configured (which seems to induce the root cause), just needed to identify which agent executed the build successfully (Agent 1 in my case) Added a tag to the agent and modified the build definition to point to the that agent.

http://social.msdn.microsoft.com/Forums/en/tee/thread/2ed2209b-7e60-4f72-863e-dd88d09ae115

 

 

Ach, sorry...forgot that I had enabled that feature as well on my side.  Removes all parallel building, though.  Happy to hear a fix is coming.