maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <bpor...@f2network.com.au>
Subject RE: Maven Return Codes in a Continuous Integration environment
Date Wed, 13 Aug 2003 23:49:39 GMT
Cruise control's maven integration works fine for test and build failures.
I'm not sure that it is using exit codes though - it is probably just
grepping for "BUILD FAILED" at the end. Can't say for certain - haven't
really checked.

- Brett

> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com] 
> Sent: Thursday, 14 August 2003 9:47 AM
> To: Maven Users List
> Subject: Re: Maven Return Codes in a Continuous Integration 
> environment
> 
> 
> 
> I've not been using Anthill, but am doing continuous 
> integration with nightly build scripts [assuming that nightly 
> counts as continuous].
> 
> I've considered an error to be the failure to produce an 
> output. So if no *ar is created as a part of the build, the 
> build failed, and if a docs/ was not made as a part of 'maven 
> site', then the site build failed.
> 
> It would be nice if Maven would set up some nice error codes 
> for different failure reasons.
> 
> 1 = DEPENDENCIES FAIL [if it exits here]
> 2 = SRC WON'T COMPILE
> 3 = TEST SRC WON'T COMPILE
> 4 = TESTS FAIL
> 
> etc etc.
> 
> The cludgy success-test might not work for you, but has 
> managed to hang together enough for my needs.
> 
> Hen
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message