[
http://jira.codehaus.org/browse/CONTINUUM-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148094#action_148094
]
Napoleon Esmundo C. Ramirez commented on CONTINUUM-1815:
--------------------------------------------------------
I tried addressing this issue with my suggestion, but it didn't work. I built
a multimodule project (with inter-module deps), and released it. When the
scheduled build triggered, nothing was built. Seems I was wrong to rely on the
build state in determining the build order. But the weird thing I observed was
the way scheduled builds treat projects with changes, as it was different when
forcing a build. I can't say anything definite yet, I just based it on the
event logs. I'm digging deeper into this.
> Scheduled build loses track of proper reactor order after a release
> -------------------------------------------------------------------
>
> Key: CONTINUUM-1815
> URL: http://jira.codehaus.org/browse/CONTINUUM-1815
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
> Affects Versions: 1.1
> Reporter: Napoleon Esmundo C. Ramirez
> Priority: Minor
> Fix For: 1.3
>
>
> After a release, the scheduled build fails because the build order doesn't
> start with the parent. The parent doesn't get built first because the last
> build status of the parent is already green--and so builds the submodules
> first. To work this out, a manual build should be triggered.
--
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
