TFS通过分支构建vNext版本控制 [英] TFS Builds vNext Versioning by branch
问题描述
目前我使用TFS作为存储库，并且对于每个活动分支，我们都有一组在它们之间具有不同版本的构建，因此，我们可以随时从MAIN升级到DEV安装，但不能以其他方式升级。
示例：
分支主页
BuildA - 1.0.0.0
BuildB - 1.0.0.0
分支DEV：
BuildA - 1.0.1.0
BuildB - 1.0.1.0
现在，我们正在考虑转向GIT，并且TFS vNext中有一个机会可以针对不同的分支进行独特的构建和编译。但我似乎无法找到一个简单的解决方案，在它们之间拥有独特的构建和不同的版本。
我如何实现这一目标？你们有更好的解决方案吗？不需要这个吗？
嗨P. Alves，
感谢您在此发帖。
抱歉，不能帮到你。你真正的要求是什么？从TFVC转到Git？或者使用分支名称来构建版本？请澄清要求，然后我们可以相应地给出建议。
通常，TFS用于源代码版本控制。根据你的描述似乎你正在使用Build存储，如果我误解，请纠正我。
如果我是对的，那么为了存储构建，TFVC与Git类似。 TFS vNext具有针对不同分支的唯一构建和编译，适用于TFVC和Git。
如果要使用vNext构建，可以设置
构建格式，因此需要进行版本控制，例如：
（ TeamProject）_
（BuildDefinitionName）_
Currently I use TFS as Repository, and for every active branch we have a set of builds with different versioning between them so, at any moment we can upgrade from MAIN to DEV installations but not the other way.
Example:
Branch Main:
BuildA - 1.0.0.0
BuildB - 1.0.0.0
Branch DEV:
BuildA - 1.0.1.0
BuildB - 1.0.1.0
Now, we are thinking moving to GIT, and there is an oportunity in TFS vNext to have a unique build and compile against different branches. But I can't seem to find a simple solution to have unique builds and different versions between them.
How can I achieve this? Do you guys have a better solution to not needing this?
Hi P. Alves,
Thank you for posting here.
Sorry, cannot get you very well. What’s your real requirement? Move from TFVC to Git? Or version the build with branch name? Please clarify the requirements, then we can give the suggestions accordingly.
Generally, TFS is used for source code version control. According to your description seems you are using for Build storing, correct me if I misunderstand.
If I am right, then for storing the build, TFVC is similar as Git. TFS vNext to have a unique build and compile against different branches is applied to both TFVC and Git.
If you want to build with vNext , you can set the build format as versioning needed accordingly, eg :
(TeamProject)_
(BuildDefinitionName)_
这篇关于TFS通过分支构建vNext版本控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
