|
|
|
[
Permlink
| « Hide
]
Robin Shen [01/May/14 02:31 PM]
Closing due to the reason commented. Feel free to reopen it if you think there is a reason for this behavior.
This seems appropriate for most cases we've seen now. Normally user uses the "trigger build step" to trigger a dependency, and the master build should be failed if any of its current dependency is failed even if the dependency build is not being triggered recently. This also happens when a dependency of configuration is set up via via QuickBuild repository.
|