You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by David Neiman <dn...@cellexchange.com> on 2006/06/14 17:43:44 UTC
Problem updating from CVS on scheduled builds
I'm new to continuum. Have successfully configured and run Ant builds both
scheduled and forced but now getting the following build failure ONLY with a
scheduled build which seems to be related to the CVS update as indicated in
the continuum.log. This is not encountered on a forced build.
Also, the same schedule is assigned to two build definitions within the same
project.
:pserver:dneiman@osco:/cvsroot -q log -d '">2006-06-14T11:05:19-0400"'
4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
Updated 10 files.
4279313 [Thread-2] INFO
org.apache.maven.continuum.buildcontroller.BuildController - The project
was not built because all changes are unknown.
Re: Problem updating from CVS on scheduled builds
Posted by Emmanuel Venisse <em...@venisse.net>.
The forced build for a schedule build is a planned feature for 1.1
Emmanuel
David Neiman a écrit :
> I think I've fixed this problem but came up with another.
> It seems the CVS source tree wasn't clean somehow (see extended log below).
>
> So now that I've cleaned them up I get the following on a scheduled build:
> 9053308 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
> Executing: cvs -z3 -f -d :pserver:dneiman@osco:/cvsroot -q update -d
> -rFVM_13_2_BRANCH
> 9053308 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
> directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
> 9056993 [Thread-2] INFO
> org.apache.maven.continuum.buildcontroller.BuildController - The project
> was not built because there are no changes.
>
> When I do a forced build on the project the build happens regardless, even
> if there are no files updated from CVS.
>
> Is there a way to configure Continuum to do the build even though there are
> no changes? There are multiple builds (different EAR files created) that
> happen on the same schedule. These won't happen since only the first build
> definition gets the updated files.
>
> Thanks.
>
>
>
> 5333099 [defaultScheduler_Worker-4] INFO
> org.apache.maven.continuum.build.settings.SchedulesActivator -
>>>>>>>>>>>>>>>>>>>>>> Executing build job (test_build)...
> 5333109 [defaultScheduler_Worker-4] INFO
> org.apache.maven.continuum.Continuum - Enqueuing '5VM' (Build definition
> id=2).
> 5333189 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
> Updating project: id: '1', name '5VM' with branch/tag FVM_13_2_BRANCH.
> 5333269 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
> Executing: cvs -z3 -f -d :pserver:dneiman@osco:/cvsroot -q update -d
> -rFVM_13_2_BRANCH
> 5333269 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
> directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> src/appconfig
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> src/certs
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> src/etc
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> src/sql
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> src/hibernate/gen
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> src/mil/navy/fvm/client
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> test/tools/webservice test tool/FvmClient/WebRoot/WEB-INF/classes/localhost
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> test/tools/webservice test tool/FvmClient/WebRoot/WEB-INF/classes/mil
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> test/tools/webservice test tool/FvmClient/src/localhost
> 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
> test/tools/webservice test tool/FvmClient/src/mil
> 5337365 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
> Executing: cvs -z3 -f -d :pserver:dneiman@osco:/cvsroot -q log -d
> '">2006-06-14T13:07:03-0400"'
> 5337365 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
> directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
> 5337485 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
> Updated 10 files.
> 5337605 [Thread-2] INFO
> org.apache.maven.continuum.buildcontroller.BuildController - The project
> was not built because all changes are unknown.
>
>
>> -----Original Message-----
>> From: Emmanuel Venisse [mailto:emmanuel@venisse.net]
>> Sent: Wednesday, June 14, 2006 12:25 PM
>> To: continuum-users@maven.apache.org
>> Subject: Re: Problem updating from CVS on scheduled builds
>>
>> Can you send more logs? like the list of updated files. Perhaps they are
>> in an unknown state.
>>
>> Emmanuel
>>
>> David Neiman a écrit :
>>> I'm new to continuum. Have successfully configured and run Ant builds
>> both
>>> scheduled and forced but now getting the following build failure ONLY
>> with a
>>> scheduled build which seems to be related to the CVS update as indicated
>> in
>>> the continuum.log. This is not encountered on a forced build.
>>>
>>>
>>>
>>> Also, the same schedule is assigned to two build definitions within the
>> same
>>> project.
>>>
>>>
>>>
>>> :pserver:dneiman@osco:/cvsroot -q log -d '">2006-06-14T11:05:19-0400"'
>>>
>>> 4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
>> Working
>>> directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
>>>
>>> 4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
>>> Updated 10 files.
>>>
>>> 4279313 [Thread-2] INFO
>>> org.apache.maven.continuum.buildcontroller.BuildController - The
>> project
>>> was not built because all changes are unknown.
>>>
>>>
>>>
>>>
>
>
>
>
>
>
RE: Problem updating from CVS on scheduled builds
Posted by David Neiman <dn...@cellexchange.com>.
I think I've fixed this problem but came up with another.
It seems the CVS source tree wasn't clean somehow (see extended log below).
So now that I've cleaned them up I get the following on a scheduled build:
9053308 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
Executing: cvs -z3 -f -d :pserver:dneiman@osco:/cvsroot -q update -d
-rFVM_13_2_BRANCH
9053308 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
9056993 [Thread-2] INFO
org.apache.maven.continuum.buildcontroller.BuildController - The project
was not built because there are no changes.
When I do a forced build on the project the build happens regardless, even
if there are no files updated from CVS.
Is there a way to configure Continuum to do the build even though there are
no changes? There are multiple builds (different EAR files created) that
happen on the same schedule. These won't happen since only the first build
definition gets the updated files.
Thanks.
5333099 [defaultScheduler_Worker-4] INFO
org.apache.maven.continuum.build.settings.SchedulesActivator -
>>>>>>>>>>>>>>>>>>>>> Executing build job (test_build)...
5333109 [defaultScheduler_Worker-4] INFO
org.apache.maven.continuum.Continuum - Enqueuing '5VM' (Build definition
id=2).
5333189 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
Updating project: id: '1', name '5VM' with branch/tag FVM_13_2_BRANCH.
5333269 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
Executing: cvs -z3 -f -d :pserver:dneiman@osco:/cvsroot -q update -d
-rFVM_13_2_BRANCH
5333269 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
src/appconfig
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
src/certs
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
src/etc
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
src/sql
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
src/hibernate/gen
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
src/mil/navy/fvm/client
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
test/tools/webservice test tool/FvmClient/WebRoot/WEB-INF/classes/localhost
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
test/tools/webservice test tool/FvmClient/WebRoot/WEB-INF/classes/mil
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
test/tools/webservice test tool/FvmClient/src/localhost
5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ?
test/tools/webservice test tool/FvmClient/src/mil
5337365 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
Executing: cvs -z3 -f -d :pserver:dneiman@osco:/cvsroot -q log -d
'">2006-06-14T13:07:03-0400"'
5337365 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
5337485 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
Updated 10 files.
5337605 [Thread-2] INFO
org.apache.maven.continuum.buildcontroller.BuildController - The project
was not built because all changes are unknown.
> -----Original Message-----
> From: Emmanuel Venisse [mailto:emmanuel@venisse.net]
> Sent: Wednesday, June 14, 2006 12:25 PM
> To: continuum-users@maven.apache.org
> Subject: Re: Problem updating from CVS on scheduled builds
>
> Can you send more logs? like the list of updated files. Perhaps they are
> in an unknown state.
>
> Emmanuel
>
> David Neiman a écrit :
> > I'm new to continuum. Have successfully configured and run Ant builds
> both
> > scheduled and forced but now getting the following build failure ONLY
> with a
> > scheduled build which seems to be related to the CVS update as indicated
> in
> > the continuum.log. This is not encountered on a forced build.
> >
> >
> >
> > Also, the same schedule is assigned to two build definitions within the
> same
> > project.
> >
> >
> >
> > :pserver:dneiman@osco:/cvsroot -q log -d '">2006-06-14T11:05:19-0400"'
> >
> > 4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager -
> Working
> > directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
> >
> > 4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
> > Updated 10 files.
> >
> > 4279313 [Thread-2] INFO
> > org.apache.maven.continuum.buildcontroller.BuildController - The
> project
> > was not built because all changes are unknown.
> >
> >
> >
> >
Re: Problem updating from CVS on scheduled builds
Posted by Emmanuel Venisse <em...@venisse.net>.
Can you send more logs? like the list of updated files. Perhaps they are in an unknown state.
Emmanuel
David Neiman a écrit :
> I'm new to continuum. Have successfully configured and run Ant builds both
> scheduled and forced but now getting the following build failure ONLY with a
> scheduled build which seems to be related to the CVS update as indicated in
> the continuum.log. This is not encountered on a forced build.
>
>
>
> Also, the same schedule is assigned to two build definitions within the same
> project.
>
>
>
> :pserver:dneiman@osco:/cvsroot -q log -d '">2006-06-14T11:05:19-0400"'
>
> 4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working
> directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1
>
> 4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
> Updated 10 files.
>
> 4279313 [Thread-2] INFO
> org.apache.maven.continuum.buildcontroller.BuildController - The project
> was not built because all changes are unknown.
>
>
>
>