[
http://jira.codehaus.org/browse/CONTINUUM-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190432#action_190432
]
Wendy Smoak commented on CONTINUUM-1286:
----------------------------------------
Is this still a problem in the latest release?
> better control with trigging of builds through dependencies
> -----------------------------------------------------------
>
> Key: CONTINUUM-1286
> URL: http://jira.codehaus.org/browse/CONTINUUM-1286
> Project: Continuum
> Issue Type: Improvement
> Components: Core system
> Affects Versions: 1.1-alpha-1
> Reporter: Eirik Maus
>
> seems like a build for a dependent module is triggered each time a dependency
> is built. This seems to cause modules several levels down in the dependency
> graph to be built many times for the same change in a root module (propagated
> once for each intermediate dependency relation). A module should not be added
> to the build queue if it already is in the build queue.
> Also, if scm timestamps are propagated through the builds (seperate jira
> issue), it would easily be confirmed that the dependent module already is in
> the build queue with the same timestamp, and that one build of the module
> would be sufficient. Today it would be several builds, each from head with a
> few minutes between, with modules near the end of the dependency chain being
> built often and against different scm timestamps than the intermediate
> modules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
