Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

TFS Labels, confused by the Changeset column

Tags:

tfs

I use Labels in TFS so as to keep track of my deliveries. The Build service also labels each build, which is OK

However, in the Labels window (History / Labels), the column named 'ChangeSet' has a weird content, with always the same number displayed (which is the very first Changeset number of the codebase, by the way), regardless of the Changeset chosen while creating the label.

Do anyone have the same behaviour? Any hints on why this particular Changeset number is displayed?

Thanks

like image 840
Vinzz Avatar asked Nov 27 '13 12:11

Vinzz


People also ask

What is the use of labels in TFS?

With labels, you can also apply later changesets to an existing label if there were code changes by simply getting that label and then getting specific changesets and then doing a quick label or creating a brand new label. Labeling is very powerful, convenient to use, and is a part of TFS.

Who wrote the code to show changesets between labels in TFS?

Carl Daniel ( code) and Robert Downey ( code) each wrote and posted code to show the changesets between two labels in TFS version control.

Why not use TFVC labels instead of changesets?

First, using TFVC Labels is MORE resource intensive than using changesets. A lot more. Commands such as Branch, Merge, and Get by Label is slower. For enterprise servers with huge databases you do not want to be using labels. Second, Builds don't automatically create labels, although the default build steps include a step to create a label.

What is the difference between a changeset and a label?

4 Answers 4. They have two different purposes, ChangeSets are when the files have actually changed and you wish to keep a permanent record of that change. Labels mark a certain version of the files so that you can easily go back to that point. Unless your build actually changes files under source control and you wish to record these changes.


1 Answers

That column shows the version of the files and folders at the time they were for the changeset selected. So for a folder, its the changeset of the folder itself, and not anything within the folder.

It can be a bit confusing, but if you are labeling at a high directory level in source, it's likely that the container the label was applied to hasn't been changed since the first changeset. So you will always see that first changeset number.

If you open that label and drill down to where the changed files are, you will see the changeset numbers are your more recent changesets.

like image 69
malexander Avatar answered Sep 21 '22 21:09

malexander