Team build - 'enlistment is empty'

Question

I have two team projects defined, and I've previously created a team build for one of them.

Now, when I try to create a new team build in either team project I get a diaglog that says "Enlistment is empty.  The workspace "server" does not have any working folder mappings (where server is replaced with the name of my TFS server).

One oddity that I note - in the source controll explorer, the "workspace" is named the same as the client machine, while the Team Build error dialog is griping about a workspace named the same as the TFS app-tier machine.  What's a 'workspace' in this context?  Where are they defined?  How can I view/edit them?

Both team projects have associated solutions checked into their source control branch.  What's this message trying to tell me?   What can I do about it?

Answer 1

A workspace is a container in source control that holds your workspace mappings (mappings that say where things in the server go on your hard drive), your pending changes, and what files you have (in TFS, the server knows which files and which versions you have on your disk).

To see your workspaces, go to File-> Source Control -> Workspaces... in VS.  The resulting dialog will show your workspaces to you.  In the beta release, it will show you all of the workspaces that you own, not just the ones on that machine.  Click on the workspace that team build mentioned in the error message and click the Edit button.

The error message is complaining that without having any mappings, it doesn't know where the files in the server should go on your disk.  Although I'm not too familiar with team build, try adding a mapping that maps $/ to the location on disk where you solution exists.

Buck

Answer 2

By the way, it would be better to post this question in the Team Foundation forum in order for more Team Foundation folks to see it.

Buck

Answer 3

Carl,

The error, 'Enlistment is empty.' means that the workspace 'server' does not have at least one mapping from the server folder to the local disk.

Can you look at the workspace mappings for the workspace that is named the same as the client machine and the workspace called 'server'? You can do this by opening Source Control Explorer (View->Other Windows->Source Control Explorer) and then navigating to File->Source Control->Workspaces. Edit the workspace and note all working folders that are listed.

In the beta2 release there is a restriction on a workspace that is being used for a build that it must have folder mappings to only one portfolio project. So you will have to remove any folder mappings listed that do not reference the portfolio project that you are trying to create the build type for. (you can identify the portfolio projects mapped into by looking at the entry in the 'Repository folder' column, which will usually be of the form $/Portfolio Project/<Folder>

Alternatively, you can create a new workspace that has mappings exclusively to the portfolio project which you want to build for by using File->Source Control->Workspaces->Add and manually adding the folder mapping entries from the UI or using the command line tool. After that you should be able to select this workspace in the workspace selection page when creating the new build type for the portfolio project.

Answer 4

Indeed, under Source Control there's a Workspaces... option.  Choosing that option shows one workspace, named the same as my client machine.  Choosing that workspace shows the enlishtments for the two team projects I've created.  Everything OK there.

When I try to create a new team build, however, it complains that the enlishment is empty, and the workspace it refers to is named the same as the app tier server.  No such workspace exists, so naturally the enlistment is empty.

Something's broken!  Why is the New Team Build Type... machinery coming up with the wrong workspace name?

Answer 5

That was the key tidbit - a workspace cannot span two team projects.  Is that restriction going to be fixed in RTM?

Answer 6

Note that the workspace itself can have mappings to multiple team project. However, the build system currently requires a workspace to have mappings to a single team project. 

And yes, this restriction has been removed post beta2.

Answer 7

i m on Beta3 but couldn't see the fix.
i mapped the root($/)  to local folder so that all team project can be mapped to it.