[JIRA] Updated: (HUDSON-2456) Automatically imply Jabber server suffix in per job 'Targets' field

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-2456) Automatically imply Jabber server suffix in per job 'Targets' field

Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kutzi updated HUDSON-2456:
--------------------------

    Summary: Automatically imply Jabber server suffix in per job 'Targets' field  (was: Automatically imply Jabber server suffix in 'target' field)

> Automatically imply Jabber server suffix in per job 'Targets' field
> -------------------------------------------------------------------
>
>                 Key: HUDSON-2456
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-2456
>             Project: Hudson
>          Issue Type: Improvement
>          Components: jabber
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: rickb007
>            Assignee: kutzi
>            Priority: Minor
>
> The jabber plugin allows messages to be sent upon certain events. This is useful
> but limited. In particular, the notification strategy option allows any one of
> 'all', 'failure' or 'change', but does not allow any combination of these.
> It would be more generally useful in larger project teams if there were some
> configurable matrix of jabber IDs agains the possible events that can cause a
> message to be sent.
> One simple way to implement this might be to to replace the existing 'targets'
> and 'notification strategy' inputs with two targets fields: one for 'failure',
> and one for 'change'. Also, add a third target field for 'success' notifications
> (typically, a QA person might be interested only in successful builds for example).
> A better way would be to have an extending list (e.g. similar to the extending
> list of Subversion repository locations).  This would effectively for a matrix:
> each row would start with a jabber ID and would have tick-boxes for 'success',
> 'failure' and 'change'. It would be possible to add new rows to the table and
> change or delete existing rows.

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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]