JetBrains TeamCity Blog

This isn’t a brand new feature, but one might not yet know that besides email, Jabber, rss, IDE and Windows tray notifications, you can configure TeamCity to sent notifications about builds status via Google Talk instead of Jabber.

The only thing you need to do is to set the following options on the Administration | Server Configuration | Jabber Notifier tab:

• Server: talk.google.com
• Port: 5222
• Server user/password to send notifications from.

Note, that if you use Google Apps for domain, you should specify full username with domain part in the Server user field. Naturally, these settings are available only for System Administrators.
As with the rest notifiers, you can tune up the messages sent: the FreeMarker templates used for generating them are fully customizable (refer to our docs for the details).
Once this is done, a user will need only to specify his account and notification rules at My Settings&Tools | Jabber notifier tab to subscribe to Google Talk notifications.

Enjoy!

TeamCity provides several ways of getting notified about your builds’ status, like e-mail notifications, Jabber/XMPP instant messages and more. All the notifiers allow flexible customization to fit your needs.

However, there are other ways to keep track of your projects. For example, Scott Cowan has created TeamCity Twitter Notifier plugin. The installation is easy, and providing that Twitter allows to create private accounts, you can keep project notifications both restrictive and accessible. So if you like to twit, give it a try!

By the way, check the list of the plugins for TeamCity – you may find something interesting for you, or try to create your own.

Sincerely,
The JetBrains TeamCity Team

New TeamCity 5.1 EAP build is available, which brings several noteworthy improvements and contains a lot of bug-fixes. The major improvement concerns build triggers:

• Starting with this EAP, you can enble/add triggers to build configurations based on a template, which previously was not possible. Additionally, build triggers UI has become more convenient.
  
• Moreover, build triggers are now pluggable, i.e. it is possible to add custom build trigger with custom web UI, read more.

Plus, there are several other improvements you might find interesting:

• Ability to run personal build with custom parameters from Eclipse plugin.
• Support for NAnt 0.90 alpha 1.
• Same archive name can be specified multiple times in the right part of the artifacts settings, i.e.:
  **/*.html => report.zip
**/*.css => report.zip!/css/
• Improved notification templates.

Take a look at the release notes, check the complete list of changes, and try the build. Just to be on a safe side, do not forget to back up your data before upgrade.

As usual, feedback is appreciated.
The JetBrains TeamCity Team