Hi, After a few days of bug hunting with Emmanuel, we finally found out what's happening. On our instance we have basically two project groups:
# Project Group A with schedule S1 responsible of building the projects # Project Group B with schedule S2 responsible of deploying the site We're using CVS and adding two build definitions on the same group didn't work because the changelog functionnality is broken (known problem with some versions of CVS). Maybe Emmanuel can explain this better but it is impossible to add the same project (i.e. same groupId, artifactId, version) twice, even if they are in different schedule. I understand the technical difficulty, however: * If it's not supported, a check should be added to avoid confusion * If duplicate projects are removed, it would be nice to remove the projects that does *not* belong the current active schedule (hence if A is building, we should remove duplicate from B and vice-versa). Thoughts? Thanks, Stéphane On 3/5/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi, Since a few days, my Continuum instance (1.1-SNAPSHOT 20070214) does not build some of my projects anymore. I've tracked it down to one particular project (the most active!) that was not built since 28th Feb. This is the very first project I added in continuum (project Id = 1). I searched in the logs any info regarding this projec tId and ... nothing since the 28th of February. They are changes to the project of course and I've restarted continuum several times without no noticeable change. This morning I decided to force the build, the project had 56 changes (in CVS). I have the feeling that the project is not enqueued anymore. For my EVERY_4_HOURS schedule, I have more than 20 projects linked to it. In my logs, here's what I have 27062449 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (EVERY_4_HOURS)... 27062656 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Blah' (Build definition id=7). 27062661 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build 27062662 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Foo' (Build definition id=11). 27062667 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Bar :: Utilities' (Build definition id=2). 27062673 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Bar :: Data Access' (Build definition id=2). 27062678 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Help plugin' (Build definition id=7). 27062683 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Plop plugin' (Build definition id=7). 27062687 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Starting build of Build info generator 27062689 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Required info generator' (Build definition id=7). 27062693 [defaultScheduler_Worker-2] INFO org.apache.maven.continuum.Continuum - Enqueuing 'Samples :: Stuff API' (Build definition id=12). Where the hell are the others? Am I missing something? How come that the build job does not enqueue *All* projects that have this scheduling? Any help/feedback is greatly appreciated. Thanks, Stéphane
