Hi Owen,
I used it in slightly different manner. On SVN (using
atomic commits).
[sorry for old syntax - I didnt upgrade production server
yet]:
<schedule type="schedule"
sleepSeconds="600"/>
<modificationDelaySeconds>120</modificationDelaySeconds>
I used this to enable more "atomic" commits to build
together. Since if someone make change in several subprojects (which all are
groupped into one ccnet project), he/she will commit it into repository with
several commits, e.g.:
commit into A with message 'added new property Name
into remoting interface'
commit into B with message 'added new overloaded
constructor with Name parameter, Name property and name data
store'
commit into C with message 'added new form filed into web
page enabling to enter name of component'
commit into D with message 'added new extra parameter Name
to web service'
All those commits go one after other, with some pause
between them. No need to compile just A and B+C+D after A is built. So
modificationDelaySeconds efectivelly wait for other commits and it will build
all of them. Does it make sense?
Anyways - IMHO it is related to polling trigger, since it
delays build triggered for some time and make another poll.
| |
|
|
|
| |
GORDIC spol. s. r.o., Erbenova 4, 586 01 JIHLAVA
Tel: 567 309
136, 567 303 601 |
|
hi martin,
> reminds me - what about to move
modificationDelaySeconds to trigger? It is
property of trigger, isn't
it?
not exactly. the modificationDelaySeconds
property is used to implement the quiet period for non-atomic source controls.
if you are using svn or perforce, you should never need to worry about
this property.
the quiet period is a
window of time during which detected modifications are considered to be at
risk of being part of an ongoing commit. to rephrase: if i'm using a
non-atomic source control system like cvs and ccnet detects that files were
checked in 2 seconds ago, i can't be sure whether or not there are more files
to come as part of the current commit. if i start a build at this point,
it might break because the ccnet local workspace only some of the changed
files.
hopes this clarifies
things,
owen.
---
R. Owen Rogers
ThoughtWorks Technologies
(India) Pvt Ltd.
ThoughtWorks - Deliver with
passion!
ThoughtWorks is always looking for talented people who are
passionate about technology. To find out more about a career at
ThoughtWorks go to http://www.thoughtworks.com/career/.
|
| "Martin Aliger"
<martin_aliger-BTyGo4b3k76lVyrhU4qvOw@xxxxxxxxxxxxxxxx>
Sent by: ccnet-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
18/11/2004 20:22
Please respond to ccnet-devel
|
To:
"'Mike Roberts'" <mike.b.roberts-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
cc:
<ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx>, (bcc:
Owen Rogers/Canada/ThoughtWorks)
Subject:
[Ccnet-devel] RE: [Ccnet-user] Source not checking out with
StarTeam |
Hi,
this
> <triggers>
>
<pollingInterval seconds="60" />
>
</triggers>
>
<modificationDelaySeconds>120</modificationDelaySeconds>
reminds
me - what about to move modificationDelaySeconds to trigger? It is
property
of trigger, isn't it?
<triggers>
<pollingInterval seconds="60"
modificationDelaySeconds="120"/>
</triggers>
Martin Aliger
> -----Original
Message-----
> From: ccnet-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
>
[mailto:ccnet-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On Behalf Of
> Mike
Roberts
> Sent: Thursday, November 18, 2004 2:39 AM
> To: Carlton
Nettleton
> Cc: ccnet-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> Subject: Re:
[Ccnet-user] Source not checking out with StarTeam
>
> On Wed, 17
Nov 2004 17:05:51 -0800, Carlton Nettleton
>
<cnettleton-8jgFHlqHMNsFQeE35raUng@xxxxxxxxxxxxxxxx> wrote:
> > It appears I cannot seem
to get the source to check out of
> StarTeam.
>
>
Hi Carlton,
>
> I assume you are using CruiseControl.NET
0.7?
>
> I can't help much with the StarTeam problem - look at
the
> debug log on the CruiseControl.NET server process and see
> that it is performing a 'starteam co', maybe try running this
> process manually from the command line and see if it works.
>
> > Also, no build is started when there has been a change to
> the repository. Did I forget to set something up? How
would
> I tell CC.Net to wait 120 seconds (or whatever) after the
> last check-in to execute a build? Thank you in advance for
> all your help.
>
> You need a <triggers> section
and a <modificationDelay> - see
>
http://confluence.public.thoughtworks.org/display/CCNET/Config
>
uring+the+Server.
>
> Something like the following should do you
:
>
> <triggers>
>
<!-- Poll the SCM server every 60 seconds to see if > there are any
updates -->
> <pollingInterval seconds="60"
/>
> </triggers>
>
>
<!-- Wait at least 2 minutes before doing a build after > someone has
checked anything in -->
>
<modificationDelaySeconds>120</modificationDelaySeconds>
>
>
>
-------------------------------------------------------
> This SF.Net
email is sponsored by: InterSystems CACHE FREE
> OODBMS DOWNLOAD - A
multidimensional database that combines
> robust object and relational
technologies, making it a
> perfect match for Java, C++,COM, XML, ODBC
and JDBC.
> www.intersystems.com/match8
>
_______________________________________________
> Ccnet-user mailing
list
> Ccnet-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
>
https://lists.sourceforge.net/lists/listinfo/ccnet-user
>
>
-------------------------------------------------------
This
SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A
multidimensional database that combines
robust object and relational
technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and
JDBC.
www.intersystems.com/match8
_______________________________________________
Ccnet-devel
mailing
list
Ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ccnet-devel
