You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/05/05 06:02:44 UTC
[jira] Created: (CONTINUUM-2217) Scheduled builds stopped after
upgrade
Scheduled builds stopped after upgrade
--------------------------------------
Key: CONTINUUM-2217
URL: http://jira.codehaus.org/browse/CONTINUUM-2217
Project: Continuum
Issue Type: Bug
Affects Versions: 1.3.3
Environment: 1.3.3-SNAPSHOT r768185
Reporter: Wendy Smoak
We upgraded vmbuild.apache.org to Continuum 1.3.3-SNAPSHOT r768185 and it looks like no scheduled builds have happened since then.
Details on https://issues.apache.org/jira/browse/INFRA-2037
--
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
[jira] Commented: (CONTINUUM-2217) Scheduled builds stopped after
upgrade
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176218#action_176218 ]
Maria Odea Ching commented on CONTINUUM-2217:
---------------------------------------------
I took a look at the projects causing the ".. is duplicated error 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 error.
> Scheduled builds stopped after upgrade
> --------------------------------------
>
> Key: CONTINUUM-2217
> URL: http://jira.codehaus.org/browse/CONTINUUM-2217
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: 1.3.3-SNAPSHOT r768185
> Reporter: Wendy Smoak
> Priority: Critical
> Fix For: 1.3.3
>
>
> 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
--
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
[jira] Commented: (CONTINUUM-2217) Scheduled builds stopped after
upgrade
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176213#action_176213 ]
Maria Catherine Tan commented on CONTINUUM-2217:
------------------------------------------------
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.
> Scheduled builds stopped after upgrade
> --------------------------------------
>
> Key: CONTINUUM-2217
> URL: http://jira.codehaus.org/browse/CONTINUUM-2217
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: 1.3.3-SNAPSHOT r768185
> Reporter: Wendy Smoak
> Priority: Critical
> Fix For: 1.3.3
>
>
> 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
--
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
[jira] Issue Comment Edited: (CONTINUUM-2217) Scheduled builds
stopped after upgrade
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176218#action_176218 ]
Maria Odea Ching edited comment on CONTINUUM-2217 at 5/12/09 10:00 PM:
-----------------------------------------------------------------------
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.
was (Author: oching):
I took a look at the projects causing the ".. is duplicated error 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 error.
> Scheduled builds stopped after upgrade
> --------------------------------------
>
> Key: CONTINUUM-2217
> URL: http://jira.codehaus.org/browse/CONTINUUM-2217
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: 1.3.3-SNAPSHOT r768185
> Reporter: Wendy Smoak
> Priority: Critical
> Fix For: 1.3.3
>
>
> 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
--
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
[jira] Commented: (CONTINUUM-2217) Scheduled builds stopped after
upgrade
Posted by "Jevica Arianne B. Zurbano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176500#action_176500 ]
Jevica Arianne B. Zurbano commented on CONTINUUM-2217:
------------------------------------------------------
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.
> Scheduled builds stopped after upgrade
> --------------------------------------
>
> Key: CONTINUUM-2217
> URL: http://jira.codehaus.org/browse/CONTINUUM-2217
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: 1.3.3-SNAPSHOT r768185
> Reporter: Wendy Smoak
> Priority: Critical
> Fix For: 1.3.3
>
>
> 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
--
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
[jira] Updated: (CONTINUUM-2217) Scheduled builds stopped after
upgrade
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-2217:
-----------------------------------
Priority: Critical (was: Major)
Description:
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
was:
We upgraded vmbuild.apache.org to Continuum 1.3.3-SNAPSHOT r768185 and it looks like no scheduled builds have happened since then.
Details on https://issues.apache.org/jira/browse/INFRA-2037
Fix Version/s: 1.3.3
> Scheduled builds stopped after upgrade
> --------------------------------------
>
> Key: CONTINUUM-2217
> URL: http://jira.codehaus.org/browse/CONTINUUM-2217
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: 1.3.3-SNAPSHOT r768185
> Reporter: Wendy Smoak
> Priority: Critical
> Fix For: 1.3.3
>
>
> 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
--
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
[jira] Closed: (CONTINUUM-2217) Scheduled builds stopped after
upgrade
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak closed CONTINUUM-2217.
----------------------------------
Assignee: Wendy Smoak
Resolution: Fixed
I believe this was fixed by CONTINUUM-2219. Scheduled builds are happening again on vmbuild.
> Scheduled builds stopped after upgrade
> --------------------------------------
>
> Key: CONTINUUM-2217
> URL: http://jira.codehaus.org/browse/CONTINUUM-2217
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: 1.3.3-SNAPSHOT r768185
> Reporter: Wendy Smoak
> Assignee: Wendy Smoak
> Priority: Critical
> Fix For: 1.3.3
>
>
> 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
--
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