我们可以在perforce中创建标签吗 [英] Can we create Labels in perforce

问题描述

我在一个项目中工作.我们同时使用clearcase和perforce.

I am working in a project. We use both clearcase and perforce.

由于我们正在开发不同的网络版本，因此，在明显的情况下，我们为每个发行版创建一个标签.对于发行版"X"，我们创建一个透明的保护套"Label X".标签X具有与版本"X"有关的所有最新文件.当我们完成另一个发布时，说"Y"，我们创建另一个标签，说"Label Y".标签"Y"再次具有发布"Y"的所有文件.但是在任何时候，我们都可以返回到"Label X".这意味着所有文件都将还原为"Label X".

As we are working on differnet builds, In clearcase we create a label for each release. Say for release "X", we create a clearcase case "Label X". Label X is having all the latest files with respect to release "X". When we finish another release say "Y", we create another label say "Label Y". Label "Y" is again having all the files for release "Y". But at any point of time we can go back to "Label X" .It means all the files will be reverted back to "Label X".

我们可以在perforce中做同样的事情吗?我们可以在perforce中创建标签吗?因此，在任何时间点，我们都可以转到该标签，该标签将按照该标签的时间轴显示文件.

Can we do same thing in perforce? Can we create a label in perforce so at any point of time, we can go to that label which will give the files as in that label timeline.

推荐答案

Perforce还提供了一个有趣的指南"p4 label不是唯一的选择:

Perforce also provide an interesting guide "Migration Planning Guide: IBM Rational ClearCase to Perforce", and mention that p4 label is not the only alternative:

ClearCase和Perforce均提供标签，用于标识构成基准的文件的版本.对于许多ClearCase用户，标签是必需的.应用标签非常耗时，通常占创建时间的30％或更多 稳定的构建.

Both ClearCase and Perforce provide labels, which identify the versions of files that constitute a baseline. For many ClearCase users, labels are mandatory. Applying labels is time-consuming, often accounting for 30 percent or more of the time associated with creating stable builds.

在Perforce中，标签只是复制基准的一种方法. 更改列表以与构建标签无关的方式实现了相同的目标，与标签相比，该方法对构建过程的负担更少，并且引用起来更快，更容易.

In Perforce, labels are just one way of reproducing baselines. Changelists accomplish the same goal in ways that are less taxing on the build process and faster and easier to reference than a label.

每个Perforce签入都会生成一个唯一的变更列表编号，该编号反映了某个时间点上存储库的状态.任何变更列表都可以用来描述状态 存储库中每个文件的大小，即使它仅影响存储库中的一小部分.

Each Perforce check-in generates a unique changelist number that reflects the state of the repository at a point in time. Any changelist can be used to describe the state of every file in the repository, even though it affects only a small subset of the repository.

这太简单了，因为典型的配置规范是几行或更多行.
Perforce中的分支表示为目录，可以轻松地将分支和变更列表编号组合起来以表示基线.
或者，标签可以引用更改列表编号，该更改列表编号限于服务器中已确定的范围，该范围通常是特定的分支.

This is an oversimplication since a typical config spec is several lines or more.
Branches in Perforce are represented as directories, making it easy to combine branches and changelist numbers to represent a baseline.
Alternately, labels can refer to changelist numbers limited to an identified scope in the server, where the scope is typically a particular branch.

这篇关于我们可以在perforce中创建标签吗的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！