continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Napoleon Esmundo C. Ramirez (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-1815) Scheduled build loses track of proper reactor order after a release
Date Tue, 23 Sep 2008 07:01:45 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148771#action_148771
] 

Napoleon Esmundo C. Ramirez commented on CONTINUUM-1815:
--------------------------------------------------------

Some more observations:

1. Added the multimodule project in continuum
2. forced a build of the project group (build order was correct)
3. released the project group
4. wait for a scheduled build (build order was correct, but skipped building the parent)


> 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
>
>         Attachments: multimodule-project.tar.gz
>
>
> 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

        

Mime
View raw message