TFS标签与詹金斯一个Build连续环境 [英] TFS Labels in a Build Continuous Environment with Jenkins

问题描述

我们正在提高构建连续的环境我们与詹金斯构建过程。
我们有运行每一个开发者提交code时间持续构建工作。
一个重要的问题是今天提出：
我们可以申请一个TFS标签为每个成功的构建？

We are improving our build process with Jenkins in a build continuous environment. We have a continuous build job that runs every time a developer commit code. An important question was raised today: Could we apply a TFS label for each success build ?

多少标签将一个文件夹结构，并支持
当我想看看历史的标签，如果TFS将显示所有他们所有的时间，或者如果它有一个专家的算法只显示最近X的。
如何性能可以与大量的标签为每个成功构建被影响。 （我们估计，每天将超过10/20签入，产生10/20构建和每天10/20标签）。
而更多的，是有一些方法来过滤VS历史窗口标签？

How many labels will a folder structure supports and when I’d like to see the history labels, if TFS will show all them all the time, or if it has a expert algorithm that show only that last X ones. and how the performance could be affect with a lot of labels for each success build. (We are estimate that will be more than 10/20 check-ins per day, generate 10/20 builds and 10/20 labels per day). And more, is there some way to filter labels in VS history window?

推荐答案

是的，你可以肯定的标签使用的 tf.exe命令行，标签总是present，但在查找对话框标签可以过滤。我不认为他们会影响性能反正除了查找标签对话框。然而，在TFS构建系统也删除标签构建，当他们删除历史版本，所以你可能会试图维护以及删除所有标签过去的某一天，因为在所有诚实，如果你正在标记10-每天（或每构建）正是在这些标签值的20倍？标签不会在历史窗口显示，那些变更集（签入），并有对标签没有任何关系。标签是一块用来标识在整个工作区的每个文件的版本，以便在某些时候，如果你需要重建，或检查的所有文件可以按照标签拉下code和看到的元数据在这个构建工作区的确切状态。你真的需要为所有20个做到这一点建立一个日子？还是有特殊的构建这是用来创建安装程序或包会去QA /舞台/生产？您可能会发现更多有用的只有这些标签生成。

Yes, you could certainly label using the tf.exe command line, labels are always present, but can be filtered in the find labels dialog. I don't think they would affect performance in anyway except in the find labels dialog. However, in the TFS build system they also delete the label for a build when they delete a build from history so you may try to maintain that as well and delete all labels past a certain day, because in all honesty if you are labeling 10-20 times a day (or every build) exactly what is the value in those labels? Labels don't show in the history window, those are changesets (checkins) and have no relationship to labels. A label is a piece of meta data used to identify the version of each file across the whole workspace so that at some point if you need to rebuild it or inspect all of the files you can pull down the code by label and see the exact state of the workspace at that build. DO you really need to do this for all 20 builds a day? or are there special builds which are used to create the installer or package that will go to QA/Stage/Production? You may find it more useful to only label those builds.

这篇关于TFS标签与詹金斯一个Build连续环境的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！