Jenkins: Notifications

Notify Upstream Developers when a Downstream Build Fails

When your development team is divided into smaller sub-teams that work together closely, it is often the case that the problem introduced in a library component blows up when building/testing a bigger assembly in a downstream process. Jenkins® can track the relationship between such upstream projects and downstream projects and it can notify those upstream who made the changes, when the downstream builds started failing.

By having Jenkins send a notification directly to the responsible party, you eliminate the unnecessary human-to-human communication overhead.

Reduce the Notification Spam

Unlike traditional cron jobs, Jenkins is smart about when to send notifications to people. For example, if you have a streak of successful builds, no e-mail gets sent as nothing needs to be acted upon. But if the build status changes from one state to another, an e-mail will be sent.

By being smart about when to send notifications, Jenkins gets developers’ attention when it is really needed.

Failure Notification to Developers Who Break a Build

While Jenkins can be told to send e-mails to a certain fixed set of addresses, it is more useful to tell Jenkins to send an e-mail solely to the developer who broke the build. That is, developers who make a commit that went into a failed build. People no longer get a “build is broken” e-mail if they have nothing to do with the failure. This is just one more way Jenkins enhances developer productivity–by leaving you alone, unless something occurs that you really need to know about.

Get the Notifications the Way You Want with Plugins

Install plugins to receive notifications in ways that suit you–IRC, Google Talk, tray application, RSS, Twitter and so on. Or have fun with extreme feedback devices (XFD) that make your work environment more colorful!

The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc.