Build Monitor Features
These are software features only. For a feature comparison with the various models of the optional USB siren see Features.
| Siren of Shame | TFS Build Monitor | Team City Build Monitor | |
|---|---|---|---|
| Alerts |  |
||
| Open Source | |
||
| Easy to use | |
|
|
| Check-In Comments | |
||
| Statistics, build history | |
||
| Configurable polling interval | |
||
| Countdown of estimated build time | |
||
| Rules engine | |
|
|
| Multiple Connections | |
||
| Full screen mode | |
||
| Configuration within the app | |
What does a build monitor look like?
Well, here's ours:
What is a Build Monitor?
A build monitor is a piece of software that continuously monitors a continuous integration server such as CruiseControl, Bamboo, Team City, Hudson, or Team Foundation Services.
When anyone checks in code to source control the continous integration server tries to compile the code and run any automated unit tests.
Should a co-worker (never you of course) check in bunk code that doesn't compile or fails the unit tests, the continous integration server will:
- Trigger a failed build
- Notify everyone by carrier pigeon
- The carrier pigeon gets struck by lightning
- But fortunately a build monitor picks up the slack and warns people immediately
So yea, unfortuantely the capabilities of most continuous integration servers are somewhat limited with respect to notifying your team. And if you are unfortunate enough to download someone's bunk code because you didn't notice the build was broken then what was the point of setting up continuous integration in the first place? Yea, waste of time. Thus the need for a nice open source build monitor like Siren of Shame. Or better yet a frickin' siren with flashing lights and stuff.
What continusous integrations servers are supported?
Right now we support:
- Team Foundation Services (TFS)
- Team City
- Hudson
- Jenkins
- and CruiseControl.Net
But the architecture is pluggable (and did we mention open source), so anyone could write an add-on.