continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] (CONTINUUM-1815) Scheduled build loses track of proper reactor order after a release
Date Tue, 20 Nov 2012 06:39:13 GMT

     [ https://jira.codehaus.org/browse/CONTINUUM-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-1815.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.4.1)
                   1.4.0 (Beta)
    
> Scheduled build loses track of proper reactor order after a release
> -------------------------------------------------------------------
>
>                 Key: CONTINUUM-1815
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-1815
>             Project: Continuum
>          Issue Type: Bug
>          Components: Web interface
>    Affects Versions: 1.1
>            Reporter: Nap Ramirez
>            Assignee: Maria Catherine Tan
>            Priority: Minor
>             Fix For: 1.4.0 (Beta)
>
>         Attachments: continuum.log, 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message