TFS 2010 Team Build Error

2
votes

I get the following TFS Team Build Error:

Could not find a part of the path 'E:\Builds\17\NextGenIssueTracker\
    NGIT-2011Updates\Binaries\QA\_PublishedWebsites\NGIT.Test.ClientProxy_Package\
    Archive\Content\E_C\Builds\17\NextGenIssueTracker\NGIT-2011Updates\Sources\
    branches\2011Updates\NGIT.Test.ClientProxy\obj\QA\Package'.

However, I've removed the project from source control, the solution, and from my local working directory. But I'm still getting this error.

Any suggestions?

Important: I don't have access to this 'E:\Builds\17" directory, so that might be a game changer!

2
visual-studiotfstfsbuild
what's the context of this error in TFS? i.e. what build step are you currently in? – Nick Nieslanik
Along with Nick: If this project is no longer under TFS, what exactly are you doing to throw that error? – NotMe
I don't believe that I'm doing anything! My local solution builds fine, but the CI triggered build fails with the above error. I have no clue why it still cares about this project... – Didaxis

2 Answers

4
votes

You are running into a limitation on the maximum amount of characters that a path can have. This is a pretty well known problem with windows.

Some options available:

  1. Change the build path to something much shorter than that.
  2. Rename the solution and, potentially, projects in the solution to shorten the path.

For all intents and purposes, the first part:

 "E:\Builds\17\NextGenIssueTracker\
    NGIT-2011Updates\Binaries\QA\_PublishedWebsites\NGIT.Test.ClientProxy_Package\
    Archive\Content\E_C"

is odd.

Sounds like you need to get with your TFS administrator to ask them what the heck that is about.

1
votes

Re-entering a comment as an answer since it fixed the problem:

Try manually triggering a build and override the settings in the dialog box to do a full workspace clean. Looks like you've got some build artifacts still lying around.