A Year of Shame

A year ago we figured we'd maybe sell a couple of these things.  But since September of 2011 we have averaged a sale of one and a half units per week.  That's 71 units to 61 Locations Worldwide.  We've shipped Siren of Shame units to thirteen countries.  We've had generous open source advocates buy us 44 beers!

Not too bad for a couple of guys working out of a basement in their spare time.  Thank you to everyone who has helped including friends, patient customers, and especially family.

And here's a cool map of locations we've shipped to:


View Siren of Shame Units Worldwide in a full screen map

How To Reset Reputation

If you've got a negative reputation in SoS Online and were considering just creating a new account, but didn't want to lose your achievements, we now have a solution.

Go to your profile page.  Click Activity.  Click the new "Reset Reputation" link.  Your reputation will reset to zero and your achievements will remain.

The only down side is that the reputation reset will be visible in the leader board activity feed.

Travis CI Support in Siren of Shame 1.6

One of the new features in Siren of Shame 1.6 is support for Travis.  If you aren't familiar with Travis it's an awesome continuous integration server that works with GitHub projects.  No dedicated server required.

The beauty of this new feature is you can now gain reputation and earn achievements on your side projects in addition to your professional work.  Even if you have two instances of Siren of Shame, one at work and one at home, if they're both syncing to SoS online your reputation and achievements will be merged for purposes of the leader boards.

Adding Travis to Siren of Shame is slightly different than other CI servers because there is no authentication and projects are based on owner name and project name rather than url.

Other than that once you've added the project it will look just like a Jenkins, Team City or any other supported CI server.

Released 1.6

We've got some awesome new features.  Here's what's new:

Achievements 
Because why not gamify continuous integration?

Some of our favorites are "CI Ninja" which you get when you fix someone else's build.  Or "Macgyver" which you get when you reduce build times by 15%.

View the full list of 23 achievements on our website.  As an existing user we'll even retroactively find achievements from the time you started using the app.  You can also now view an individual's achievements by clicking on their name:

SoS Online
What good are achievements and reputation if you can't do a little smack talk?  You can do that with the SoS Online button:

If you create a free account and click "Sync whenever I trigger a build" we'll put you on the leader boards and keep your personal page up to date:

We even have the capability to manually sync if you've got crazy firewall rules or work disconnected.

We'll provide more details on achievements and SoS online in a future post.  We hope you enjoy and would love to hear your thoughts in the comments section.

Setup
You shouldn't even notice, but switching to Wix toolset should make the setup experience as smooth as butter.

New CI Server: Travis 
That's the one that runs against GitHub projects.  We'll provide more Travis details in a future post. 

New CI Server: Buildbot
Thanks to @BubbaFatAss for this contribution.

Minor Features

• When people's reputation changes you can see the delta and a pretty fade animation
• The error dialog now allows you to specify contact information
• The firmware upgrade process is simpler there should be no more HidD_SetOutputReport bugs
• You can now connect to TFS with a named account rather than your windows account
• The SoS splash screen now displays the product version
• If SoS gets an error while retrieving build status it now assumes the server is unavailable and won't send an error report unless you click a new button in the lower left of the status bar

Bugs Fixed

• Issue #25: If you double click a build for TFS it now goes to the build status page rather than the artifact's page
• Issue #22: Dates displayed on the main page are now culture-aware (e.g. d/M in europe, M/d in the US)
• Issue #21: If you use Hudson or Jenkins with and set it's "Internal URL" incorrectly SoS no longer dies a terrible death
• Issue #20: If two builds occur simultaneously in TFS SoS no longer bugs out
• Issue #18: If you connect to TFS using someone else's credentials they are passed correctly in all API calls
• Issue #16: SoS now runs under non-admin accounts
• Issue #15: When you go back and edit the list of builds you're watching SoS defaults old watched builds to being checked
• Issue #14: If you use Hudson or Jenkins with and set it's "Internal URL" incorrectly SoS no longer dies a terrible death
• Issue #13: When you have multiple SoS instances open in different windows accounts SoS now gives a nice error message
• If Team City runs a scheduled clean up jobs it no longer confuses SoS
• If you haven't associated .log with a default app in Windows and you view the log you no longer get an error
• If you have rules to make the LED lights on the device stop sometimes they would never stop

Bug Prioritization

Bug Prioritization

Ever seen something like this while running the siren of shame software?

When you click the send button it shoots us an e-mail with the stack trace, and (as of version 1.6) some optional contact information.


Ways to Submit Bugs
This dialog represents one of three ways to submit bugs. In addition to in-app bug reports we additionally welcome your patches and pull requests, and as described in how to report bugs we accept bug reports through Google Code.


Priority
Unless we see a large number of similar errors we typically prioritize anything submitted via the in-app dialog as low. In other words we probably won’t get to it any time soon. For the fastest response we love patches and a pull requests. But we’ll also get right on that if you submit the bug via Google Code over here:

http://code.google.com/p/siren-of-shame/issues/list

That will allow us to start a dialog with you, gain context into your error, request relevant parts of your log files (see how to report bugs), try very hard to reproduce your error, and allow others with the same error to diagnose their problem and sign up for status notifications.


tl;dr
We welcome in-app bug reports, we prefer Google code issues, we really love patches pull and requests. Regardless we appreciate all your help in making Siren of Shame the best build monitor software around.

Released 1.5

Here's what's new:

Double click a build to see build details (86)

Oft-requested, finally implemented. This opens an appropriate URL, regardless of whether the build server is TFS, Team City, Jenkins, Hudson, Cruise Control, or Bamboo.

Display build id on main page (158)

Implemented across all CI servers. See screenshot above.

Can now sort builds (153)

Now you can keep the most recent builds on top rather than always sorting by name.

Added "Never Update" to configuration options (81)

Useful if you're on a disconnected network. Selecting this option will also disable retrieving alerts, so SoS will never try to get to the Internet at all.

Bug Fixes

• "Invoke or BeginInvoke cannot be called on a control until the window handle has been created" (128)
• TFS should treat partially succeeded as failed (150)
• Team City bug: Can't move focus to the control because it is invisible, not enabled, of of a type that does not accept the focus (151)
• TeamCity error: Timed out waiting for authentication was reported as a bug is now server unavailable (154)
• CruiseControl.Net wasn't returning started date in some circumstances (155)
• Importing firmware from some other cultures was causing an error when interpreting day as month (156)
• When you close the Configure Server dialog it no longer refreshes all build status if nothing actually changed (157)

Summary

Hope you enjoy the updates. You can either download verison 1.5 here or if you're on a public network it should auto-upgrade on next install.

Firmware V3

We just released a new version of the firmware that allows you to visually identify who broke a build from across the room. To accomplish this V3 contains 71 LED patterns!

Ok, technically it only contains 11 truly unique ones, but most of them have seven variations: the main pattern followed by 0-6 blinks. To identify who broke the build from across the room simply assign a number to each developer.

So imagine you get up to fix a cup of coffee, you hear the sad trombone, you glance up to see the "Jarring Flash" LED pattern, then a pause, then three blinks, then back to "Jarring Flash". Oh crap, you're developer #3. Quick, better get back to work and fix it before anyone notices.

The 11 led patterns are:

• SOS
• Slow Pulse
• Pulse
• Chase
• Dark Chase
• Fade Chase
• Random Fades
• Random
• Jarring Flash
• Dim; and
• 255

Patterns like Slow Pulse, Random Fades, and Dim would be excellent indicators that a build has been triggered, but not broken. These patterns then would be good to allow you to see who checked in from across the room.

Sadly we had to remove audio to fit these LED patterns in our (whopping) 32K of memory, so we could only fit the sad trombone into this version. But hey, shoot us a note if you'd like a custom firmware build and we'll see what we can do.