We'll publish new versions from time to time. No need to use the most recent, feel free to pick the version you like the most.
Thursday, January 26, 2012
Firmware V2
We released a new version of the firmware last week. This version provides new audio for existing siren of shame devices. Specifically it contains a sad trombone sound, a ding and a plunk. You can find the new file and instructions on the new firmware page of the site.
Thursday, January 19, 2012
How To Report Errors
Updated 3/29/2014
We have moved our issues list to GitHub, please report issues there.
Also, you can get to the logs in Siren of Shame 2.0 like this:

If you find an error please report it on the issues list of the Google Code site. When you do please provide relevant information from the logs such as a stack trace. You can get to that by clicking "View Logs..." from here:

We have moved our issues list to GitHub, please report issues there.
Also, you can get to the logs in Siren of Shame 2.0 like this:

Original Post
If you find an error please report it on the issues list of the Google Code site. When you do please provide relevant information from the logs such as a stack trace. You can get to that by clicking "View Logs..." from here:

Monday, January 9, 2012
Released 1.3
Here's what's new:
Full Screen Mode (106)
Now you can have a wall of shame to compliment your siren:

Alerts (142)
To advertise to you, isn't that awesome?
Mute Siren (134)
In case the shareholders meeting next door is trying to figure out which developers to fire.
Edit Names and Hide Users (135 & 136)
Right click a name in the reputation bar to find some new options:
New names cascades everywhere.
Bug Fixes
- Full screen mode for The Enforcer didn't restore your screensaver settings until app close (138)
- Builds are now listed alphabetically when adding (#6)
- TFS now supports multiple mappings in a workspace (#7)
- Fixed "The process cannot access SirenOfShame.config because it is being used by another process" (#140)
- Fixed "could not open the firmware upgrade file" if firmware file not present (#139)
- Can now downgrade firmware (#141)
Thursday, December 15, 2011
How To Configure Rules
Is there a little too much shame in your office? Distracting alert dialogs? Blaring sirens bothering co-workers?
Configuring Rules
The fastest way to change the default settings across all projects is to right click anywhere in the white space and navigate the menu:
Following the screenshot above and clicking on "1 Second" will toggle the setting, thus disabling the chirp-on-check-in feature.
Configuring Per Build or Per Person
If you want to configure settings for only a specific project, or an individual on a specific project, you can click on the project and navigate the menu the same way:
Following the screenshot above will decrease the amount of time that the lights flash whenever "Lee" breaks the build for the first time on "Project 1" (perhaps as build manager he breaks it frequently).
Fine Tuning
Finally if you want more control of the rules you can check the "Configure Rules" button on the main page. This will take you to the Configure Rules screen where you can double click on a rule to edit and fine tune your settings:
Summary
Shaming build breakers doesn't have to annoy co-workers. Hopefully now you are able to accomplish one without the other ... or more effectively accomplish both.
Sunday, December 4, 2011
Released 1.2.0
Summary of New Features
- Maintains build history
- Tracks user reputation
- Graphs recent build durations
- Simple per-project statistics
- Turn off or reset reputation from settings menu
Bug fixes
- Exception on adding Jenkins Jobs when Brackets "()" are part of the name (#2)
New Feature: Maintains build history
The software now maintains a history of check-ins for reporting purposes. At present it will miss anything that occurs when it's not running. In other words if you go on vacation for a week your stats will be different than your co-workers. We're working on a fix for this, but let us know if you think this is a big deal or not.
New Feature: Reputation
The goal of reputation is to add an element of good-natured competition and fun to your project while simultaneously trying to decrease the amount of time wasted resolving source control conflicts, fixing broken builds, and/or waiting on broken builds.
The idea is each person receives one point for each check-in, and loses four points for each broken build. This should do two things:
1. Encourage smaller more frequent check-ins, which will minimize check-in conflicts between team-members; and
2. Encourage team-members to run tests prior to check-in to decrease chances of breaking the build.
We intend to add more sophistication to the algorithm in a future release (e.g. incorporate code-coverage), but we would love to hear any feedback on what we have now.
If you really don't like the idea of reputation you can turn it off in settings.
New Feature: Build History
The chart on the right shows build durations for the last eight builds. A blue bar indicates a successful build. A red bar indicates a failed build. The Y axis shows duration in minutes. The X axis goes from oldest to newest. Click on a build on the left to show the chart on the right, click off a chart to go back to the user/reputation view (unless you've turned it off).
Summary
We're proud of the latest updates and we hope you'll like them. Please don't hesitate to give us feedback on twitter @SirenOfShame or via e-mail: "support" at our domain name.
Tuesday, November 29, 2011
Released 1.1.4
If you auto-updated the software within the last 12 hours and are receiving an error about a method missing in UsbLib.dll it is because we failed to update one of the dll's in the auto-update package. The msi installer was not affected by this omission. If you are in this state now will need to uninstall and reinstall the latest version.
To fix this we have released another update: 1.1.4. The primary reason was to fix our deployment mistake, but we fit in one small bug fix as well:
- Team Foundation Services now supports the PartiallySucceeded status
We have fixed our deployment process so this should not happen again. Sorry for any inconvenience.
Monday, November 28, 2011
Released 1.1.3 of the Software
Bug Fixes
- Hudson supported neither the "Unknown" nor any new/unexpected build statuses (130)
- Hudson, Team City, Bamboo, and Cruise Control don't always fail nicely when the network is down (132)
- Bamboo and Cruise Control weren't deployed in the 1.1.2 msi setup file (133)
- SOS should display a disconnected message rather than error while Hudson is initializing (131)
- Windows 8 bluetooth attach/detach caused errors (127)
- Notify text on minimize/close was annoying (129)
Subscribe to:
Posts (Atom)