Re: [Cc-config-users] Monitoring CC v2.5 doesn't show failurs

[Wick, A. <aw...@st...>]

I'll take a look at how the monitoring page determines build failure.  I
thought it was based on the same idea of using LastBuildTime.

=20

-Al

=20

________________________________

From: cc-...@li...
[mailto:cc-...@li...] On Behalf Of
Andrew Ochsner
Sent: Tuesday, June 13, 2006 3:51 PM
To: cc-...@li...
Subject: Re: [Cc-config-users] Monitoring CC v2.5 doesn't show failurs

=20

Right so I did a bit more digging. =20

The default for projects in cruisecontrol (v2.5 at least) is for
buildAfterFailure=3Dtrue.  This means that the LastBuild time won't be
updated so that CruiseControl can continually detect changes every time
it does a modificationSet. =20

But the ProjectProxy determines a failure if LastBuild !=3D
LastSuccessfulBuild which will never occur if the
buildAfterFailure=3Dtrue.

Is there any other way to detect if a project has failed other than
using LastBuild time?=20

Thanks
Andy Ochsner

On 6/13/06, Andrew Ochsner <aoc...@cs...> wrote:

Hi:

I am using cc-config v1.4 beta 1 (also happens on v.1.3)  to monitor a
CruiseControl v2.5 instance.  It seems that it never notices failures
anymore.  It says it's always successful even thought it's failing. =20

Has anyone else seen this?  Is there an easy fix to this?

Andy Ochsner

=20