RE: [Cruisecontrol-user] QuietPeriod parameter in JMX console

[Jeff D. <jef...@sh...>]

Well, I'm down to 1 minute now.  I was using 3 minutes.  You make a good
point about the possibility of not getting a build for a long time when =
the
quiet period is too long.  (We're not a team of so many developers that =
a
longer quiet period will be a problem, generally speaking.)  Conversely, =
the
down side of a quiet period that is too short is that some files may be
missing from a check in when the build is triggered resulting, =
presumably,
in a failed build.

~Jeff


-----Original Message-----
From: cru...@li...
[mailto:cru...@li...] On Behalf Of =
Jeffrey
Fredrick
Sent: Saturday, October 23, 2004 3:42 PM
To: 'Jeff Davidson'; cru...@li...
Subject: RE: [Cruisecontrol-user] QuietPeriod parameter in JMX console



ok, how about a bunny?  :)

What problem do you fear with a quiet period that is too short? What's =
the
downside of a build that is triggered w/some files not checked in?

In my experience a short quiet period is even more desirable w/more
developers rather than less desirable, or you might go a very long time
w/out a build as the quiet period is triggered again and again by more
people checking in.

I believe the default quiet period is 1 minute; what are you using?

Jtf