Issue Details (XML | Word | Printable)

Key: CONTINUUM-2217
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Wendy Smoak
Reporter: Wendy Smoak
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Continuum

Scheduled builds stopped after upgrade

Created: 04/May/09 11:02 PM   Updated: 14/May/09 11:36 PM   Resolved: 14/May/09 11:36 PM
Return to search
Component/s: None
Affects Version/s: 1.3.3
Fix Version/s: 1.3.3

Time Tracking:
Not Specified

Environment: 1.3.3-SNAPSHOT r768185
Issue Links:
Related
 

Complexity: Intermediate


 Description  « Hide

We upgraded vmbuild.apache.org to Continuum 1.3.3-SNAPSHOT r768185 on Apr 24th and it looks like no scheduled builds have happened since then.

Details on https://issues.apache.org/jira/browse/INFRA-2037



Maria Catherine Tan added a comment - 12/May/09 08:51 PM

looking at the logs from https://issues.apache.org/jira/browse/INFRA-2037, the warn message will only appear if continuum is trying to build more than one instance of the same project, with the same groupId, artifactId, version.


Maria Odea Ching added a comment - 12/May/09 09:52 PM - edited

I took a look at the projects causing the ".. is duplicated in the reactor" in vmbuild and it seems the Sling projects were added twice in the group? As for the jUDDi project, there are two groups of the project added in vmBuild.. both the projects in the two groups are similar and that's what's probably causing the "..is duplicated" warning message.


Jevica Arianne B. Zurbano added a comment - 14/May/09 10:14 PM

The warning "...duplicated in the reactor" is displayed when a project is added twice (either in different groups or the same group). Given this scenario, the scheduled build is triggered but the project scm and the projects are not updated and queued for build.


Wendy Smoak added a comment - 14/May/09 11:36 PM

I believe this was fixed by CONTINUUM-2219. Scheduled builds are happening again on vmbuild.