TFS Label Mismatch

I am working with Team Foundation Server 2012 to get the Continuous Integration assembly for working with a data warehouse. At the same time, I noticed that labeling and building with labels do not give the results that I expected. In investigating the problem, I was able to replicate the problem using only the command line arguments provided by the Team Foundation Servers command line tools. This helped me eliminate anything in the assembly definition that could affect the assembly.

So this is my problem: I have an assembly that builds 2 different projects in one assembly. It has basically two * .SLN files associated with it. I applied the shortcut to 2 assets, one in each project. Then I can execute a command to see which assets have a label. In doing so, I get the expected result. However, when I execute the command to get the assets associated with this shortcut, it retrieves only one of the two files. I checked that I can extract both files by deleting one of the projects. This is the setting that I have with the assembly definition, workspace and label

TFS paths:
$ / Dev / Project1
$ / Dev / Project2

Stage display
Project1: C: / SourceControl / Project1
Project2: C: / SourceControl / Project2

DeploymentFolder
Project1: // DevServer / SSIS / Project1
Project2: // DevServer / SSIS / Project2

The executed commands:
Apply shortcut :
tf label TestLabel $ / DEV / Project1 / PackageA.dtsx
tf label TestLabel $ / DEV / Project2 / PackageA.dtsx

Review Tag:
tf tags / format: Detailed LTestLabel

Receive from tag:
tf get / r / version: LTestLabel

After running the tf get command, I get the following results

Deployment folder: // DevServer / SSIS / Project1 contains the PackageA.dtsx file
Deployment folder: // DevServer / SSIS / Project2 contains 0 files.

It seems that there is a filter or restriction on the pulling of assets in different projects with the same label. I would expect that if I apply a shortcut to any asset in TFS, then pull the shortcuts, it should allow me to get all the assets using this application tag. Has anyone heard or experienced this? Any help provided would be greatly appreciated.

+6
source share
1 answer

You do not specify which (local) folder you use when executing get: since you do not specify the folder to receive, it implies the current equivalent:

tf get /recursive /version:Llabelname . 

If you want to get both, specify a directory containing both, for example:

 tf get /recursive /version:Llabelname $/ 

This, of course, assumes that both files in your label are displayed.

+2
source

Source: https://habr.com/ru/post/958125/


All Articles