continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Catherine Tan (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (CONTINUUM-2232) Continuum ignores duplicate projects in forced and scheduled builds
Date Fri, 22 May 2009 07:19:42 GMT

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

Maria Catherine Tan closed CONTINUUM-2232.
------------------------------------------

    Resolution: Fixed

Fixed in 
r777411 of 1.3.x branch
r777412 of trunk

- prevent addition of duplicate projects to same group
- allow duplicate projects from different group to be added in build queue during scheduled
builds
- log why project is not building during forced/scheduled build


> Continuum ignores duplicate projects in forced and scheduled builds
> -------------------------------------------------------------------
>
>                 Key: CONTINUUM-2232
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2232
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.3.2
>            Reporter: Wendy Smoak
>            Assignee: Maria Catherine Tan
>             Fix For: 1.3.3
>
>
> When there are duplicate projects being built at one time, Continuum ignores the duplicates
and only builds one of them.  (See ProjectSorter.java)  It prints a log message, but there
is nothing visible in the web ui.
> Continuum considers projects with the same groupId:artifactId:version as duplicates,
so for example you can't built both the trunk and a branch with the same version in the one
group (or even in different groups if they are on the same build schedule.)
> It should probably warn if you add duplicates to a group.
> If you click 'build all' and it is *not* going to build everything, it should tell you.
> For scheduled builds there should be some indication of why a project was not built.

-- 
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