You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2010/03/03 08:47:55 UTC

[jira] Created: (CONTINUUM-2476) Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again

Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again
-------------------------------------------------------------------------------------------------------------------------------------

                 Key: CONTINUUM-2476
                 URL: http://jira.codehaus.org/browse/CONTINUUM-2476
             Project: Continuum
          Issue Type: Bug
          Components: Distributed Builds
    Affects Versions: 1.3.5
            Reporter: Maria Odea Ching


For example, you have two build agents configured (BA1 and BA2) and you also have two schedules configured (WINDOWS_DEV_BUILD and NIGHTLY_BUILD). Now, let's say your WINDOWS_DEV_BUILD runs at 6pm, 8pm and 10pm, while your NIGHLTY_BUILD runs at 11pm. You have a set of projects which have two build definitions, BDEF1 which is attached to the WINDOWS_DEV_BUILD schedule and targeted to build at build agent BA1, and BDEF2 which is set to "always build" and is attached to the NIGHTLY_BUILD schedule and targeted to build at build agent BA2. 

At 10pm, the WINDOWS_DEV_BUILD schedule fires and queues the attached projects in BA1. Let's say the build is slow and by 11pm, some of the projects haven't finished building and were still queued. When the NIGHTLY_BUILD schedule fires, the same set of projects are added to the build queue. If you look at the Queues page, you will see that they are also queued in build agent BA1 whereas they should have been queued in build agent BA2 (where they were targeted to build).

-- 
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-2476) Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-2476:
------------------------------------

    Fix Version/s:     (was: 1.4.1 (Beta))
                   1.4.0 (Beta)

> Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2476
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2476
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.5 (Beta)
>            Reporter: Maria Odea Ching
>            Assignee: Maria Catherine Tan
>             Fix For: 1.4.0 (Beta)
>
>
> For example, you have two build agents configured (BA1 and BA2) and you also have two schedules configured (WINDOWS_DEV_BUILD and NIGHTLY_BUILD). Now, let's say your WINDOWS_DEV_BUILD runs at 6pm, 8pm and 10pm, while your NIGHLTY_BUILD runs at 11pm. You have a set of projects which have two build definitions, BDEF1 which is attached to the WINDOWS_DEV_BUILD schedule and targeted to build at build agent BA1, and BDEF2 which is set to "always build" and is attached to the NIGHTLY_BUILD schedule and targeted to build at build agent BA2. 
> At 10pm, the WINDOWS_DEV_BUILD schedule fires and queues the attached projects in BA1. Let's say the build is slow and by 11pm, some of the projects haven't finished building and were still queued. When the NIGHTLY_BUILD schedule fires, the same set of projects are added to the build queue. If you look at the Queues page, you will see that they are also queued in build agent BA1 whereas they should have been queued in build agent BA2 (where they were targeted to build).

-- 
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-2476) Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-2476:
------------------------------------

    Fix Version/s: 1.4.1

> Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2476
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2476
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.5
>            Reporter: Maria Odea Ching
>             Fix For: 1.4.1
>
>
> For example, you have two build agents configured (BA1 and BA2) and you also have two schedules configured (WINDOWS_DEV_BUILD and NIGHTLY_BUILD). Now, let's say your WINDOWS_DEV_BUILD runs at 6pm, 8pm and 10pm, while your NIGHLTY_BUILD runs at 11pm. You have a set of projects which have two build definitions, BDEF1 which is attached to the WINDOWS_DEV_BUILD schedule and targeted to build at build agent BA1, and BDEF2 which is set to "always build" and is attached to the NIGHTLY_BUILD schedule and targeted to build at build agent BA2. 
> At 10pm, the WINDOWS_DEV_BUILD schedule fires and queues the attached projects in BA1. Let's say the build is slow and by 11pm, some of the projects haven't finished building and were still queued. When the NIGHTLY_BUILD schedule fires, the same set of projects are added to the build queue. If you look at the Queues page, you will see that they are also queued in build agent BA1 whereas they should have been queued in build agent BA2 (where they were targeted to build).

-- 
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-2476) Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again

Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan reassigned CONTINUUM-2476:
----------------------------------------------

    Assignee: Maria Catherine Tan

> Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2476
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2476
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.5 (Beta)
>            Reporter: Maria Odea Ching
>            Assignee: Maria Catherine Tan
>             Fix For: 1.4.1 (Beta)
>
>
> For example, you have two build agents configured (BA1 and BA2) and you also have two schedules configured (WINDOWS_DEV_BUILD and NIGHTLY_BUILD). Now, let's say your WINDOWS_DEV_BUILD runs at 6pm, 8pm and 10pm, while your NIGHLTY_BUILD runs at 11pm. You have a set of projects which have two build definitions, BDEF1 which is attached to the WINDOWS_DEV_BUILD schedule and targeted to build at build agent BA1, and BDEF2 which is set to "always build" and is attached to the NIGHTLY_BUILD schedule and targeted to build at build agent BA2. 
> At 10pm, the WINDOWS_DEV_BUILD schedule fires and queues the attached projects in BA1. Let's say the build is slow and by 11pm, some of the projects haven't finished building and were still queued. When the NIGHTLY_BUILD schedule fires, the same set of projects are added to the build queue. If you look at the Queues page, you will see that they are also queued in build agent BA1 whereas they should have been queued in build agent BA2 (where they were targeted to build).

-- 
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-2476) Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again

Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan closed CONTINUUM-2476.
------------------------------------------

    Resolution: Fixed

Fixed in r933451
- added checks if project and build definition is already in queue or is currently preparing build or building
- select build agent based on the scm roots of the same project group
- added unit test
- fixed concurrent modification exception


> Projects are not built in the correct build agent when the project is already in the build queue and then triggered to be built again
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2476
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2476
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.5 (Beta)
>            Reporter: Maria Odea Ching
>            Assignee: Maria Catherine Tan
>             Fix For: 1.4.1 (Beta)
>
>
> For example, you have two build agents configured (BA1 and BA2) and you also have two schedules configured (WINDOWS_DEV_BUILD and NIGHTLY_BUILD). Now, let's say your WINDOWS_DEV_BUILD runs at 6pm, 8pm and 10pm, while your NIGHLTY_BUILD runs at 11pm. You have a set of projects which have two build definitions, BDEF1 which is attached to the WINDOWS_DEV_BUILD schedule and targeted to build at build agent BA1, and BDEF2 which is set to "always build" and is attached to the NIGHTLY_BUILD schedule and targeted to build at build agent BA2. 
> At 10pm, the WINDOWS_DEV_BUILD schedule fires and queues the attached projects in BA1. Let's say the build is slow and by 11pm, some of the projects haven't finished building and were still queued. When the NIGHTLY_BUILD schedule fires, the same set of projects are added to the build queue. If you look at the Queues page, you will see that they are also queued in build agent BA1 whereas they should have been queued in build agent BA2 (where they were targeted to build).

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