当在文件夹中更改文件时,GIT Source Control会触发 [英] GIT Source Control make trigger when files are changed in a Folder

查看:87
本文介绍了当在文件夹中更改文件时,GIT Source Control会触发的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我安装了CCNET,以便从GIT服务器进行自动构建。
我在这里有个大问题:
我的Git服务器仓库结构:

I installed CCNET to make autobuild from a GIT server. I have a big problem here : My Git Server Repo Structure :

   Repo.git
      ---  Module 1(Folder 1)
      ---  Module 2(Folder 2)
      ---  Module 3(Folder 3)
      ---  Module 4(Folder 4)
      ---  Module 5(Folder 5)
      ---  Module 6(Folder 6)

ccnet make触发器的顺序为Mod1-> Mod2-> Mod3-> Mod4-> Mod5-> Mod6

The ccnet make trigger follow by the order Mod1 - > Mod2 - > Mod3 - > Mod4 - > Mod5 - > Mod6

但是当CCNET触发更改时任何地方(可能在Folder 5(Module 5)中进行了更改),它仍然按照上述顺序进行构建。
我不想这样做,这将需要很多时间。
我只想构建已更改的模块。
有人请帮助我使ccnet这样做。
感谢您的阅读。

but when CCNET trigger a changes anywhere(Maybe changes make in Folder 5(Module 5)), its still make a build as above order. I dont want to do this, It will take a lot of time. I just want to make build which module has been changed. Somebody please help me to make ccnet do this way. Thanks for yours reading.

推荐答案

在Git中,如果您有多个始终独立检出的目录,则这实际上是两个不同的项目,应该放在两个不同的存储库中。您可以稍后使用 Git子模块

In Git, if you have several directories that are always checked out independently, then these are really two different projects and should live in two different repositories. You can merge them back together at a later point using Git Submodules

您可以使用修改作家任务。此任务将写入XML文件,可以从构建脚本或批处理文件对其进行评估。基于此,您可以进行构建。

An alternative approach you can use Modification Writer Task. This tasks writes to an XML file, which can be evaluated from build script or batch file. Based on this you can do your build.

这篇关于当在文件夹中更改文件时,GIT Source Control会触发的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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