本地TFS 2015 Update 3中的git过滤器 [英] git filter in on premise TFS 2015 Update 3

查看:73
本文介绍了本地TFS 2015 Update 3中的git过滤器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

如果存储库位于我们的TFS项目的git之后,则无法按源文件夹过滤存储库.构建总是拉动整个存储库.我们要分别构建的TFS项目中有多个解决方案.我们可以做到,但是很慢,因为我们无法过滤要下载的源文件夹.

If the repository is git behind our TFS project there is no way to filter the repository by source folder. The build always pull the whole repository. We have multiple solutions in the TFS project we want to build separetly. We can do it, but it is slow because we cannot filter the source folder to download.

我们无法将文件夹添加到CI触发器的另一个问题.因此,所有项目都将在任何项目推入后构建.

The other problem that we cannot add folder to CI trigger. So all the projects will be build after a push in any projects.

我知道Team Services已经支持git信息库的路径过滤器.但是,有人知道在本地TFS 2015 Update 3中针对此问题的一些解决方法吗?

I know that the Team Services already support path filters for git repository. But does anybody know some workarounds for this problem for on premise TFS 2015 Update 3?

推荐答案

在TFS 2015 update3上没有解决方案.除非将组件分成不同的存储库.多个项目必须位于自己的存储库中.所有依赖项本身就是一个项目,可以作为NuGet包进行处理.这样,如果您在依赖项项目中更改某些内容并使用CI触发器,您的整个解决方案就不会中断.

There is no workaround for this on TFS 2015 update3. Unless separate your components into different repositories. Multiple projects must be in their own repository. All dependencies is a project by it self and can be handled as NuGet packages. Then your whole solution would not break if you change something in the dependency project and using CI trigger.

此功能将在 TFS 15 中提供,并且已在VSTS上提供

This feature will ship in TFS 15 and is already available on VSTS

https://www.visualstudio.com/zh-cn/docs/build/news/2016#june-14

这篇关于本地TFS 2015 Update 3中的git过滤器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆