Simple patch for Jabber-notifications

[Roland Wilczek <r.wilczek@…>]

Here is a simple patch providing Jabber-notifications on failed or successful builds.

It relies on the slave-configuration-file, so each build-slave defines it's own "observers" in the configuration:

[jabber]
enabled = true
jid = john.doe
password = changeme
defaulthost = jabber.default.com
recipients = john.doe,mary.poppins@jabber.default.com/resource

enabled

If this key is not present, no Jabber-notification will be sent. The value is irrelevant.

jid

The Jabber Identifier used to authenticate against the Jabber-Server

password

The password used to authenticate against the Jabber-Server

recipients

Comma-separated list of Jabber-accounts to notify.

defaulthost

jid and the names in recipients may have a Jabber-domain appended as @host.tld/resource. If they do not have a domain-suffix, the value of defaulthost is used.

The patch relies on ​xmpppy installed on the build-master and is based on trunk/bitten/notify.py?rev=700​

The notifications will be send according to the settings for email-notifications in trac.ini (notification.notify_on_failed_build and notification.notify_on_successful_build). The email-notifications remain untouched; Jabber-messages are sent additionally.

[Roland Wilczek <r.wilczek@…>]

based on trunk/bitten/notify.py?rev=700​

[Roland Wilczek <r.wilczek@…>]

ah ... line 93

template_name = 'bitten_notify_jabber.txt'

is orphaned and can be deleted.