RE: [Cruisecontrol-user] Continuous rebuilds after failed build

[Jeffrey F. <JFr...@al...>]

I believe this -- immediately rebuilding -- is by design because the cause
of failure might have been temporary (rebooting a db machine for instance).

Two things you might want to consider:

  *  set the spamWhileBroken attribute to false on your email element --
that will prevent you from receiving multiple emails after a build fails.

  *  you can manually use the lastBuild flag on the command line to set the
time to your current time.  If you do that then CC won't rebuild until there
is a new modification.

Jtf

-----Original Message-----
From: Randy Coulman [mailto:RCo...@ke...]
Sent: Wednesday, October 30, 2002 11:46 AM
To: cru...@li...
Subject: [Cruisecontrol-user] Continuous rebuilds after failed build


We upgraded to CC 2.0 a couple of weeks ago, and just had our first 
failed build today.  We noticed that CC immediately started another 
build, even though we hadn't yet made modifications.

There was a previous message about this in the archives from last 
December, but it was talking about pre-2.0 CC.  The solution at the time 
was to change the lastbuild property of the modificationset element to 
be ${lastBuildAttemptTime} instead of ${lastGoodBuildTime}.  However, 
according to the docs, there isn't such a beast any more.

What is the new way to solve this problem?

Thanks,
Randy
-- 
Randy Coulman
Senior Software Engineer
Key Technology, Inc.
RCo...@ke...



-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Cruisecontrol-user mailing list
Cru...@li...
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user