Setting Up Jabber Build Notifications

We took a little time this morning to set up Jabber notifications of build failures since we now have a dedicated pairing machine with no email account (plus the sooner you find out about a failed build the better really).

It's all pretty straight forward to set up, the latest CruiseControl includes a jabber publisher so you just put the details in an it all happens. I'd suggest you put it inside an onfailure element to avoid getting a message every time a build occurs (and if you're checking in regularly that will be often).

It seems to be working really well, though I would have liked it to take longer for it to get tested out but such is life. At least it didn't take us too long to get the build fixed again.

The only problem we have is that there doesn't seem to be a way to get a notification sent when the build is fixed - ie: the first successful build after a failed build, but no other successful builds. Anyone know how to get this to happen?

2 Responses to “Setting Up Jabber Build Notifications”

  1. Doug Says:

    And the other problem is that whenever we have to reboot the build machine, Jabber misses the first failure. Annoying, but not life threatening… Annoying enough to irrate everytime the build breaks, but then maybe I care too much about the build?!? Nah! 8)


  2. Doug Says:

    And while we’re (I’m) talking about annoying. Would it kill ya to have a link back to the site (at least) after a comment has been submitted? Damn, now I have to go off into the void once again…


Leave a Reply

Alternatively, subscribe to the Atom feed.