I think I've found the problem.  When the build definition has the 'Build Fresh 
(Run always a clean checkout instead of an SCM update)' checked, the scm 
doesn't tell properly tell the build that changes have occurred, so it doesn't 
continue with the scheduled build.  I think this is because a complete check 
out of the project was performed rather than an update.  Not quite the behavior 
I was expecting.

Hope this helps,

Johnathan

>>> On Tue, Nov 13, 2007 at  1:13 PM, in message
<[EMAIL PROTECTED]>, "Johnathan Gifford"
<[EMAIL PROTECTED]> wrote: 
> I see this in the logs at every time interval I expect:
> 
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,022 
> [defaultScheduler_Worker-9] INFO  
> org.apache.maven.continuum.build.settings.SchedulesActivator:default  - 
> >>>>>>>>>>>>>>>>>>>>> 
> Executing build job (EVERY_5)...
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,022 
> [defaultScheduler_Worker-14] INFO  
> org.apache.maven.continuum.build.settings.SchedulesActivator:default  - 
> >>>>>>>>>>>>>>>>>>>>> 
> Executing build job (HOURLY)...
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,054 
> [defaultScheduler_Worker-9] INFO  
> org.apache.maven.continuum.Continuum:default 
>  - Enqueuing 'XXXX' with build definition 'default ant buildDefinition' - 
> id=21).
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,054 
> [pool-1-thread-1] INFO  
> org.apache.maven.continuum.buildcontroller.BuildController:default  - 
> Initializing build
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,069 
> [pool-1-thread-1] INFO  
> org.apache.maven.continuum.buildcontroller.BuildController:default  - 
> Starting 
> build of XXXX
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,069 
> [defaultScheduler_Worker-14] INFO  
> org.apache.maven.continuum.Continuum:default  - Enqueuing 'XXXX' with build 
> definition 'default ant buildDefinition' - id=21).
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,132 
> [defaultScheduler_Worker-9] INFO  
> org.apache.maven.continuum.Continuum:default 
>  - Enqueuing 'YYYYY' with build definition 'bld2 maven2 buildDefinition' - 
> id=6).
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,132 
> [pool-1-thread-1] INFO  
> org.apache.maven.continuum.buildcontroller.BuildController:default  - Purging 
> exiting working copy
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,132 
> [pool-1-thread-1] INFO  
> org.apache.maven.continuum.buildcontroller.BuildController:default  - 
> Performing action clean-working-directory
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,163 
> [defaultScheduler_Worker-14] INFO  
> org.apache.maven.continuum.Continuum:default  - Enqueuing 'YYYYY' with build 
> definition 'bld2 maven2 buildDefinition' - id=6).
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,194 
> [defaultScheduler_Worker-9] INFO  
> org.apache.maven.continuum.Continuum:default 
>  - Enqueuing 'YYYYY' with build definition 'bld2 maven2 buildDefinition' - 
> id=6).
> INFO   | jvm 1    | 2007/11/13 13:05:00 | 2007-11-13 13:05:00,226 
> [defaultScheduler_Worker-14] INFO  
> org.apache.maven.continuum.Continuum:default  - Enqueuing 'YYYYY' with build 
> definition 'bld2 maven2 buildDefinition' - id=6).
> 
> I have two XXXX and two YYYYY projects, so I'm not sure why we're seeing 
> four YYYYY projects in the logs for 'enqueuing'.  
> 
> Yes the source repo was updated a number of times.  I've had to manually 
> (force) the maven build to begin each time.
> 
> Hope this helps,
> 
> Johnathan
> 
>>>> On Tue, Nov 13, 2007 at 12:44 PM, in message
> <[EMAIL PROTECTED]>, "Francis De
> Brabandere" <[EMAIL PROTECTED]> wrote: 
>> anything in the logs? was your source repo updated for that maven project?
>> 
>> On Nov 13, 2007 5:54 PM, Johnathan Gifford <[EMAIL PROTECTED]> wrote:
>>>
>>> Not sure what I'm forgetting to set, but my scheduled Maven2 build 
>> definitions are not getting picked up and put into the queue for Continuum 
>> 1.1 Beta 4.  My Ant build definitions that uses the same schedule setting is 
> 
>> getting picked up and ran.
>>>
>>> Does anyone have any ideas or is this just a bug with the beta version?
>>>
>>> Thanks,
>>>
>>> Johnathan
>>>
>>>
>> 
>> 

Reply via email to