continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Flournoy (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-549) A build must always be executed when previous was in failure even if there are no changes in scm
Date Thu, 19 Jan 2006 18:57:06 GMT
    [ http://jira.codehaus.org/browse/CONTINUUM-549?page=comments#action_56367 ] 

Jamie Flournoy commented on CONTINUUM-549:
------------------------------------------

If this means what I think it means, you're saying that a build should try again and again
and again until it works. I disagree - this is a waste of machine resources and can result
in mail-bombing of the notify list. (CruiseControl behaves like this and it's a pain in the
neck!) Also, in the case of a clean rebuild, the artifacts that a developer would need to
use to diagnose the failure would be repeatedly erased.

An elegant way to satisfy this would be to only send notifications if there are changes in
build success (repeated failures would generate no additional notifications), or to just send
a message saying that no more builds will happen until either an SCM change is noticed or
someone forces a build (after they diagnose the problem and fix it).

 

> A build must always be executed when previous was in failure even if there are no changes
in scm
> ------------------------------------------------------------------------------------------------
>
>          Key: CONTINUUM-549
>          URL: http://jira.codehaus.org/browse/CONTINUUM-549
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>     Reporter: Emmanuel Venisse
>      Fix For: 1.1-alpha-1

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message