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/15 01:43:44 UTC
[jira] Created: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
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
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
[jira] Commented: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177729#action_177729 ]
Wendy Smoak commented on CONTINUUM-2232:
----------------------------------------
Jev, can you please find the issue and link it here?
When I search for this issue key in my email archives, I don't see any docs touched, and there are no related issues.
> 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
[jira] Commented: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177626#action_177626 ]
Wendy Smoak commented on CONTINUUM-2232:
----------------------------------------
Has the documentation already been updated for this behavior change, or is there a separate issue for that?
> 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
[jira] Closed: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Assigned: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan reassigned CONTINUUM-2232:
----------------------------------------------
Assignee: Maria Catherine Tan
> 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
[jira] Commented: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177728#action_177728 ]
Maria Catherine Tan commented on CONTINUUM-2232:
------------------------------------------------
It's a separate issue and i think jev already did those :)
> 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
[jira] Commented: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177567#action_177567 ]
Wendy Smoak commented on CONTINUUM-2232:
----------------------------------------
Preventing addition is fine with me.
Do we need to do anything about existing instances that already have duplicates? A user who upgrades is still going to have this problem... maybe a mention in the release notes is sufficient.
(Actually I was thinking recently that we need a "health check" utility. I'll open a separate issue for that.)
> 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
[jira] Commented: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177571#action_177571 ]
Maria Catherine Tan commented on CONTINUUM-2232:
------------------------------------------------
I don't think we need to do anything anymore with existing instances. Will just mention this in the release notes.
> 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
[jira] Updated: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan updated CONTINUUM-2232:
-------------------------------------------
Fix Version/s: 1.3.3
> 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
> 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
[jira] Commented: (CONTINUUM-2232) Continuum ignores duplicate
projects in forced and scheduled builds
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177547#action_177547 ]
Maria Catherine Tan commented on CONTINUUM-2232:
------------------------------------------------
I think we should just prevent adding duplicates to a group. WDYT?
> 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