对TFS2013源代码管理的签入触发与独立TFS Git存储库相关联的CI构建 [英] Check-ins to TFS2013 source control triggers CI build associated with separate TFS Git Repository
问题描述
我有一个 TFS 2013服务器，其中包含多个TFS团队项目集合和开发人员，他们对此很高兴。项目集合中包含一组 TFS构建关联，包括相关的CI构建，这些构建在每次签入时触发，或者在某些情况下触发滚动（累积）签入。这个过程完美无瑕，并且一直是多年的工作方式。
最近，我们引入了一个 Git存储库 也位于我们的TFS 2013服务器上，并且在我连接到我的TFS 2013服务器时显示为可从我的开发环境连接的节点。 （即它不是本地回购...）
这是由不同的开发人员使用VS2013和（主要是）Git集成，是团队资源管理器在VS2013下。
这一切都非常出色 EXCEPT .....团队1正在签入 TFS源代码管理并触发CI构建，我已经建立了针对Git存储库？团队1中的任何一次提交都会导致构建触发，尽管他们正在修改不属于Git repo的代码，但从来没有，也从不会！
我现在不得不退回到手动构建，这并不理想，因为我真的需要有一个CI构建来运行测试。
就流程模板而言，我们对标准Git构建模板进行了轻微修改，我认为这是从ALM游侠所做的工作中衍生出来的 - 修改是触发InRelease部署的额外步骤。我不确定这是否相关，但为了详细讨论这个问题....
有人对我如何解决问题有任何想法这个？实质上，我想在涉及构建时完全隔离TFS和Git源代码控件。
a href =https://stackoverflow.com/a/32262306/675826>其他人已经与微软沟通过，发现这是一个错误我的建议是将你的服务器升级到最新版本。如果问题存在，请联系Microsoft支持。
I have a TFS 2013 server with several TFS team project collections and developers working happily against them. The project collections have a set of TFS builds associated, including relevant CI builds which trigger on each check-in, or in some cases, rolling (accumulated) check-ins. This process works flawlessly and has been the way of working for several years.
Recently, we've introduced a Git repository into the mix which also sits on our TFS 2013 server and appears as a node that I can connect to from my development environment when I connect to my TFS 2013 server. (i.e. it's not a local repo...)
This is being used by a different set of developers all using VS2013 and (mostly) the Git integration that is part of Team Explorer under VS2013.
This is all working fabulously EXCEPT..... team 1 are checking into TFS source control and triggering CI builds that I have set up against the Git repository?. Every single commit by any of team 1 is causing the build to trigger, despite the fact that they are modifying code that is NOT part of the Git repo, has never been and never will be! I've had to fall back to "manual" builds for now, which is not ideal because I really need to have a CI build to run tests.
In terms of the process template, we are using a slight modification to the standard Git build template which I think was derived from the work done by the ALM rangers - the modification is an extra step to trigger an InRelease deployment. I'm not sure if this is relevant or not, but in the interest of being detailed on the issue....
Anybody got any ideas of how I can fix this? In essence, I want to isolate the TFS and Git source control entirely when it comes to the builds that are triggered.
Other people have already communicated this with Microsoft and found that this is a bug
My suggestion would be to upgrade you're server to the latest version. If the problem resides, contact Microsoft Support.
这篇关于对TFS2013源代码管理的签入触发与独立TFS Git存储库相关联的CI构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
