[jira] Issue Comment Edited: (CONTINUUM-1815) Scheduled build loses track of proper reactor order after a release

["Wendy Smoak (JIRA)" <ji...@codehaus.org>]

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

Wendy Smoak edited comment on CONTINUUM-1815 at 5/10/09 9:19 PM:
-----------------------------------------------------------------

http://svn.apache.org/viewvc?view=rev&revision=699165 includes:

{noformat}
 +        //CONTINUUM-1815: additional check for projects recently released
 +        if ( !continuumProject.getVersion().equals( project.getVersion() )
 )
 +        {
 +            getLogger().info( "Found changes in project's version ( maybe project was recently released ), building" );
 +            return true;
 +        }
{noformat}

This is causing problems in CONTINUUM-1979, because the release triggers the next scheduled build (which is a release) in an endless loop.


      was (Author: wsmoak):
    http://svn.apache.org/viewvc?view=rev&revision=699165 includes:

 +        //CONTINUUM-1815: additional check for projects recently released
 +        if ( !continuumProject.getVersion().equals( project.getVersion() )
 )
 +        {
 +            getLogger().info( "Found changes in project's version ( maybe project was recently released ), building" );
 +            return true;
 +        }

This is causing problems in CONTINUUM-1979, because the release triggers the next scheduled build (which is a release) in an endless loop.

  
> 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
>            Assignee: Maria Catherine Tan
>            Priority: Minor
>             Fix For: 1.2.1
>
>         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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira