Understanding Labels



Understanding Labels


Understanding Labels

Information in this Brief applies to:

  • All StarTeam Versions
  • All Platforms


Understanding the functionality of each label type will help you to determine which label is appropriate for your process.


  • Revision Label - A revision label provides a convenient method of identifying a revision of an item or a set of revisions by name. This is primarily used for files. For example, when you check in a group of files that may need to be checked out together, you can give them a revision label.
  • View Label -The main purpose of a view label is to ?time stamp? the entire contents of the view. Then you can roll back the view to that label and see everything that existed at that point in time. However, unless the view label is frozen, you can make some adjustments. You can include or exclude some folders and items from the view label by attaching or detaching the view label. You can also move a view label from one revision to another. For example, a couple of files might not have been checked in prior to the creation of the label but need to be included.

    View labels are automatically and immediately attached to all folders and items in the view at the time they are created.
  • Build Label - When you create a view label, you can designate it as a build label. Build labels change the setting for the Addressed In field for newly resolved change requests from Next Build to the build label. This lets testers know that a resolved change request can be tested by installing that build.

Also, Promotion States can only be based upon build labels.

Old KB# 28378
Comment List