“触发快照依赖性中的改变”似乎不能正常工作 [英] "Trigger on changes in snapshot dependencies" does not seem to work properly

查看:211
本文介绍了“触发快照依赖性中的改变”似乎不能正常工作的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用TeamCity 6.5.1与一个项目和约10个构建配置。我有一个依赖链类似于Core - > Framework - > Apps。框架依赖于Core,而应用程序依赖于Core和Framework。



我遇到的问题是框架/应用程序没有在核心之后触发已被成功触发和构建。我已经在框架和所有应用程序上选择了触发对快照依赖项的更改,但是它们似乎都不会触发,即使核心构建是从SVN提交触发的。



触发快照依赖项中的更改不会像我认为的那样工作吗?是否需要将核心(和框架)VCS根添加到framework / apps上的VCS触发器?如果这是我唯一的选择,我想我可以这样做,但它似乎是多余的(特别是如果我需要调整VCS根路径在未来)。



核心VCS触发器:

  +:root = MySVNRoot:/ Core / ** 
/ pre>

Framework VCS Trigger(Core上的快照):

  [x]触发快照依赖项的变化

+:root = MySVNRoot:/ Framework / **

App VCS Trigger(Core和Framework上的快照库)

  [x]快照依赖项的更改

+:root = MySVNRoot:/ Applications / MyApplication / **


解决方案

决定在框架和应用配置中使用完成构建触发器。我更喜欢VCS触发以上述方式工作,但我会一直这样,直到有人可以建议一个更好的选择(或者如果完成构建触发真正是最好的选择)。



框架触发器:

  VCS触发
完成构建在核心上触发

应用触发器:

  VCS触发
完成对框架的构建触发器


I'm using TeamCity 6.5.1 with one project and about 10 build configurations. I have a dependency chain akin to Core -> Framework -> Apps. Framework has a dependency on Core, and the Apps depend on both Core and Framework.

The issue I am having is that the framework/apps are not being triggered after the core has been triggered and built successfully. I have selected "Trigger on changes in snapshot dependencies" on the framework and all the apps, but none of them seem to trigger even though the core build was triggered from an SVN commit.

Does "Trigger on changes in snapshot dependencies" not work the way I think it does? Do I need to add the core (and framework) VCS roots to the VCS trigger on the framework/apps? If that is my only option I suppose I could do it that way, but it seems redundant (especially if I need to adjust VCS root paths in the future).

Core VCS Trigger:

+:root=MySVNRoot:/Core/**

Framework VCS Trigger (snapshot dep. on Core):

[x] Trigger on changes in snapshot dependencies

+:root=MySVNRoot:/Framework/**

App VCS Trigger (snapshot dep. on Core and Framework)

[x] Trigger on changes in snapshot dependencies

+:root=MySVNRoot:/Applications/MyApplication/**

解决方案

Decided to use "Finish Build" triggers on the framework and apps configurations. I would prefer that the VCS trigger worked in the way described above, but I'll go with this until someone can suggest a better alternative (or if "Finish Build" triggers really are the best option).

Framework triggers:

VCS trigger
Finish Build trigger on Core

App triggers:

VCS trigger
Finish Build trigger on Framework

这篇关于“触发快照依赖性中的改变”似乎不能正常工作的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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