[Anthill] Build status

[sten.rosendahl at sungard.com]

You still would want to be able to show the results of the error/warning
scan in a build dashboard in a standard way. I would personally want a
customizable log scanner written in Java (including counting the number
of errors and warnings) as an optional task bundled with Ant.

Sten Rosendahl

-----Original Message-----
From: anthill-bounces at lists.urbancode.com
[mailto:anthill-bounces at lists.urbancode.com] On Behalf Of Robert E
Dobbins
Sent: Wednesday, November 03, 2004 3:34 PM
To: Anthill user list
Cc: Anthill user list; anthill-bounces at caladin.urbancode.com
Subject: Re: [Anthill] Build status


Probably a better approach (easier too) would be a like I have done on a
couple of projects. An alternate build file is used to drive the build-
after the build completes a perl script is launched to scan the build
output for certain strings. If the strings are found you can fail the
build, or alternatively send an email to a user or group if there are
warnings. Changing the 1 0 concept of a build being successful or failed
to include a somewhat successful is counter productive for Anthill as a
whole I would think because ou would then need a mechanism to weight and
evaluate the somewhat completes for application releases that include
several projects.

Just a thought - 

Thanks,

Robert E. Dobbins
IBM Global Services
Systems Management Integration Professional
Web Hosting
redobbin at us.ibm.com



Eric Minick <eric at urbancode.com>


Eric Minick <eric at urbancode.com> 
Sent by: anthill-bounces at caladin.urbancode.com 
11/03/2004 09:25 AM Please respond to
Anthill user list


To
Anthill user list <anthill at caladin.urbancode.com>


cc



Subject
Re: [Anthill] Build status



Jim,

I'd be interested in hearing if anyone's done this either. I think it 
would be fairly uncharted waters though. The failed status doesn't even 
check the log for error messages. It just checks the return codes from 
the commands it's running.

Good luck with it,

Eric

Jim Hague wrote:

>As I understand it, Anthill has two build result states, Green (build
>succeeded) and Red (build failed).
>In an ideal world I'd also like an Orange state - build succeeded but
with
>warnings. As far as I can see the only way to determining this state
would
>be to search the build log for 'warning' strings, so compiler specific
>patterns would be required.
>Before I even think of looking at this, has anyone ever done any
>experimenting along these lines?