continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (CONTINUUM-466) Jabber notification sends message after every build, not after a build state change
Date Fri, 10 Feb 2006 13:21:47 GMT
     [ http://jira.codehaus.org/browse/CONTINUUM-466?page=all ]
     
Emmanuel Venisse closed CONTINUUM-466:
--------------------------------------

      Assign To: Emmanuel Venisse
     Resolution: Fixed
    Fix Version: 1.0.3

Already fixed.

> Jabber notification sends message after every build, not after a build state change
> -----------------------------------------------------------------------------------
>
>          Key: CONTINUUM-466
>          URL: http://jira.codehaus.org/browse/CONTINUUM-466
>      Project: Continuum
>         Type: Bug

>     Versions: 1.0.1
>  Environment: All
>     Reporter: Marcus Crafter
>     Assignee: Emmanuel Venisse
>     Priority: Minor
>      Fix For: 1.0.3

>
>
> Hi There,
> Hope all is going well.
> With the update of Continuum to 1.0.1 we were able to get the Jabber notification support
up and running which is great, however unlike the mail notification component that sends an
email only on build state change (eg. when a build breaks, or was broken but  starts succeeding),
the Jabber notification component sends a message upon every build. With the default scheduler
 this is 1 per project, every hour.
> It would be great if the Jabber/etc notification component followed the Mail convention,
to only send out a message if the build state changes.
> Cheers,
> Marcus

-- 
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