Wednesday, February 25, 2015

Introducing Team CI Pro - 8 New Feature's You'll Love

Today we are very proud to announce our biggest change in almost two years: it's a new service called Team CI Pro.


The CI Problem


You're trying to improve software quality.  You implement continuous integration.  You're lucky, you have a motivated team that rarely breaks the build and religiously fixes breaks.  If this is you, Siren of Shame probably adds a some fun around the office, but is mostly a toy.  In this case you likely don't need most of what Team CI Pro offers (skip to Curl to Siren, below).

If you're like the rest of us your team or program breaks the build with some regularity, fails to fix it quickly, requires nagging, and/or avoids fixing builds when someone else caused the break.  If this is you, our new Team CI Pro service will provide the extra motivation your team needs to realize the full potential of continuous integration.

If it Ain't Broke?


But why a new service?  Today, at little to no cost, you can increase build awareness by throwing builds up on a dedicated monitor with our free desktop app and full-screen feature.  You can light up a siren when the build breaks.  You can require that everyone download desktop clients to get the motivating stats and gamification information.

You could even mandate that everyone sign up for My CI to get build information, stats, and gamification information pushed to their e-mail and phones for free.




But what if you don't have the authority to require your team members do anything?  How do you deal with team members less passionate about CI, and far less likely to install another app, than you?  And what if you have a distributed team that can't all see the siren or the dedicated monitor?

Even if you could mandate desktop clients and My CI for all, there's a bigger problem.  If a desktop client instance is turned off it can get out of sync.  For instance when developer #1 goes on vacation for a week, their client misses a week's worth of reputation changes and achievements from their team mates.

It's hard to brag about your superior reputation or "Consecutive Successful Build (FSB)" score when everyone has different numbers.

Feature #1 - Consolidated Accounts


Team CI Pro inherently addresses these problems with an architecture designed around a single instance of the desktop client.



Continuous integration data flows in from the CI server (bottom right) through a single desktop client (and maybe fewer, see A Shameful Future below for details) into Siren of Shame Online.  The desktop client sync's its stats and achievements to SoS Online, where the information is distributed to team members through a variety of mediums.

To facilitate distributing information to team members, teams maintain a single Team CI Pro master account on Siren of Shame Online.  Desktop clients sync to the master account in the SoS Online menu as if they were doing My CI.



Once that master account has signed up for Team CI Pro (via the 'start free trial' button at of the Team CI Page) it can access a configuration page where it can add team member accounts that will receive the master account's data.


Team members added to the configuration page gain access to a number of cool new features.

#protip - Syncing to a team master account and adding yourself as a team member allows your team to continue with Team CI Pro in the event you ever leave the team.

Feature #2 - Reputation Over Time


While the web client isn't new, Team CI Pro adds some new features.  Team members will get a new chart at the bottom of their Team CI page so they can see reputation over time.


Feature #3 - Team Heckling


Team Members will also get the ability to chat (via the blue floating button in the bottom left).  Chat messages are sent as news items to Shame Extruders (see below), mobile clients, and other web clients in realtime so team members can taunt, brag, heckle, or worst case discuss actual work.



Feature #4 - Web Full Screen Mode


All web clients now get a new full screen view (via the leftmost red button in the screenshot above).  The page is fully responsive and is designed to look good at tiny phone resolutions as well as large, high-dpi displays.

The full screen page could easily replace the full screen view in the desktop client and teams could throw identical build data up on multiple information radiators around the office, or around multiple distributed offices.  Just hit F11 (or Command+Control+F).


Feature #5 - Personalized Mobile Clients

The Android, iOS, Win Phone, and Windows Store mobile clients today show your build information, your placement and stats among a large list of virtual strangers on the SoS Online Leaderboard, and a list of news items that mostly don't relate to you or your team.  

Members of Team CI Pro will immediately have news items replaced with only news items relevant to your project (build events, achievements of fellow team members, and chat messages).  

Team CI Pro members will also see their placement and stats among just their team members.  The end result is the data displayed will be more meaningful and engaging.


And of course Team CI Pro members will continue to receive push notifications about build events and badge updates with the number of currently broken builds just like they did with My CI.

Feature #6 - Shame Extruders


A very exciting new feature for Team CI Pro members are Shame Extruders.  Shame Extruders are lightweight desktop clients that give team members all the benefits of desktop clients without any of the polling (updates are sent via SignalR).

Specifically team members can install the Shame Extruder from our download page to get

  • Tray notifications
  • Build status, leaderboards, and news
  • The ability to connect USB Sirens (see the data flow diagram earlier)
  • Team chat



They can even configure rules


While nice for individuals Shame Extruders make it even easier to install multiple sirens in different rooms or at different locations around an office with a large or distributed team.

Feature #7 - Weekly Recap E-mails


My CI sent team leads e-mails when achievements were unlocked or builds broken (including stats like highest CSB attained).  Team CI extends these features by sending e-mails directly to appropriate team members.

Better yet it provides a weekly recap e-mail with overall pass/fail ratio and a summary of team members standings and delta's to help maintain the team's continued focus on quality.



Feature #8 - Curl To Siren


We're extremely excited by the potential of this last feature.  Curl to Siren allows the master account to light up any siren in their network that's connected via a shame extruder by hitting a REST based URL.

To make it work fire up a Shame Extruder, log on as the team owner account or a team member, and connect a USB siren.  Now navigate to the master account's My CI page.  The red button furthest left should have a badge with the number of Extruder's connected.



When you click you can select "test" to fire a quick default audio and led pattern.  Or if you click the "curl" button you'll be presented with a CURL builder that will allow you to build the exact command you can run from the command line on any computer in the world to light up that siren.


You can extrapolate how you would light up the siren via JavaScript or your favorite language, but let us know if you have difficulty and we'll be glad to help.

This feature should enable you to integrate sirens into all kinds of things.  Stock ticker watchers, e-mail notifiers, room busy indicators, train schedules, or ifttt.  We can't wait to hear what you come up with.

Pricing


Pricing starts as low as $10 per month for small teams.  Check out our pricing page for more details.

Or better yet try it out at no cost for a month. It's one click to get started.  No credit cards, or DNA samples required.

A Shameful Future 


We've got some exciting things in the works, but limited resources.  Please vote here to let us know what you'd like to see us work on next:

https://www.surveymonkey.com/r/W73C6S2

Shame Extruder for Mac - Right now the Shame Extruders are for Windows clients only.  Vote for this option if you use a Mac and like Team CI Pro, but the web and mobile options aren't cutting it.

Team CI On Premise - Behind a firewall but still want all that Team CI Pro goodness?

Bluetooth Controlled Power Plug - For integrating lava lamps, model trains, or other on/off items into your CI pipeline.  This is actually prototyped out and just about ready to go.

Shame Whisperer - Wouldn't it be great to cut out polling and the Desktop Client all together?  Shame Whisperers are Plugins to CI servers that send data up to Siren of Shame Online.

Productized Raspberry Pi - You can hook your siren up to a Raspberry Pi today with some fiddling.  Wouldn't it be great if you could buy a pre-configured Raspberry Pi or download an image to turn your siren into an IoT device with virtually no effort?  Even cooler with curl to siren.

Full Desktop Client for Mac - This is expensive and time consuming, but if a Shame Extruder and/or a Shame Whisperer isn't right for you we're ready to start work on a native Mac client today.

Slack Integration - If you use Slack and want your gamification data integrated vote for this.

What Else? - There's a write in option.  Please submit any other great ideas, we'd love to hear them all.

Summary


We've put a lot into these features and hope you love them.  We hope you'll check out the free trial.  We've also got some exciting plans for what's next, and we hope you'll help us choose our next direction.  As always please let us know what you think in the comments, on twitter, facebook, or google+.

Wednesday, January 7, 2015

Released 2.3.10

We just released version 2.3.10 to prod.  If you were on 2.3.7 (our last non-beta version) you now get:

Support for Team City 9.X
This was generously contributed by @tupac21354

A Slew of TFS Fixes

  • TFS was showing "IndividualCI" instead of the author and comment while build definitions were building. This has been fixed and a large part of the TFS logic rewritten (Issue #53
  • Fixed an issue in TFS where you couldn't easily select all build definitions (Issue #44

And Some Misc Fixes

  • Fixed SOS was ignorning "Never check for updates (Issue #50
  • Fixed a bug where you can't set "Who I Am" in the settings page 

Summary

Short and sweet this time.  Please shoot us a note at support at our domain name if you need help or drop a bug on github if you find any issues.

Thursday, October 30, 2014

Released 2.3.7

We just released verison 2.3.7 and took the 2.3.x line out of beta.  If you've been sticking with the more stable 2.2 line then you now have the following features and bug fixes to look forward to:

TFS 2013


We now support Team Foundation Server 2013 including the new Git based projects.  You may also be happy to learn we fixed some issues we had with watching builds from multiple project collections.  You can also search and add new builds more easily for those with large TFS repo's.

Travis Pro and Enterprise


We now support Travis Pro and Travis Enterprise.

Jenkins


If you have a large Jenkins repository you can now filter and select all nodes more easily.

CruiseControl.Net


CruiseControl.Net now returns comments and build names.  Big thanks to Benoit Martin (benoit808) and Jonathan Ritchie for these contributions.

Bug Fixes



  • The chat box in news now only appears if you're a Team CI member - in which case it allows you to chat with your team only (What is Team CI? More on this later.)
  • Fixed the issue with adding and playing custom .mp3's when you had upgraded via wyGet
  • You can now type your username in "Who I Am" rather than having to wait until you perform a build (Issue #47)
  • The full screen shortcut key ("F") is now Alt-F, fixing a problem with using that character while chatting :)
  • Fixes performance issues when watching many builds (see Issue #38 and Issue #16 on Github)
  • When a build definition is unavailable, Team City no longer breaks (thanks @monovo for this contribution)
  • In TeamCity when one build fails to connect we now return unknown build status rather than mark the entire server an unavailable (Issue #24)

Summary

That's it for now.  This update sets the stage for a big announcement we'll have shortly.  In the meantime thanks for all your support!

Sunday, September 14, 2014

Released 2.3.4 with Travis Pro / Enterprise Support

We just released version 2.3.4 which adds support for Travis Pro and Travis Enterprise.

Unfortunately setting up authentication isn't as straightforward as it could be.  To set up a private repository:

Configure Server in Sos

  1. Add Server, Select Travis
  2. Enter your Owner and Project
  3. Select a type of Public, Private (Pro), or Enterprise
  4. If you select Enterprise enter the full url to your domain (e.g. https://travis.example.com/api/)


Generate a Travis API Access Token
  1. Click "Generate New Auth Token"


  2. Follow the instructions on the page.  Specifically:
  3. Open GitHub's Application Settings
  4. Generate New Personal Access Token
  5. Give it a name and select the following scopes: repo, user:email, write:repo_hook, repo:status, read:org, repo_deployment
  6. Click Generate Token
  7. Copy the token's value and paste it into the textbox
  8. Click "Generate Token" and we will initiate a request to Travis (using the URL you specified on the previous screen) to create a travis API access token.
  9. Upon success the new travis api access token will be entered into the textbox on the configure server page and you can click "Add" and then "Add" again

Bug Fixes

  • Can now open up the Sounds menu from a fresh install 
  • When a build definition is unavailable, Team City no longer breaks (thanks @monovo for this contribution)

Summary

We hope you enjoy the new features.  Shoot us a note at support at our domain name if you need help or drop a bug on github if you find any issues.

Tuesday, July 15, 2014

Raspberry Pi Powered Siren of Shame via Node.js

If you have a spare Raspberry Pi sitting around (and who doesn't) or are seeking an excuse to buy that newly released Model B+ model with 4 USB ports, then have you considered combining it with a Siren of Shame to hassle your build breaking office mates whether you're at the office or not?  If that sounds good this article is for you.

Getting Started


You'll need a Siren of Shame device and a Raspberry Pi that's running and connected to the Internet.  Element14 has a great getting started set of videos if you're completely new to Raspberry Pi.  This post used the Raspbian OS, but theoretically it shouldn't matter what OS you use.

libusb


Libusb provides an API for applications to interface with USB devices, including Human Interface Devices (HID) such as the Siren of Shame.  To install libusb use apt-get (the universal Linux installer).

If this is a new Raspberry Pi with a fresh install of Linux then you will need to update your list of available packages with

sudo apt-get update

Follow that up with:

sudo apt-get install libusb-dev

You should now be able to run lsusb from the command line to list devices.  Plug in a Siren of Shame, run lsusb, and you should get a device with an id of 16d0:0646 called GrauTec.  It should look like:

lsusb

...
Bus 001 Device 011: ID 16d0:0646 GrauTec

If your device doesn't show up, it could be an issue with the cable.  Andy Lowry, who has an excellent blog post where he lights up his siren of shame when freight trains are near, reports that he had to try several cables before finding one that worked.

Node.js


Thanks exclusively to Joe Ferner and his node-sos-device project we have a solution for connecting Siren of Shame's to linux using Node.js.  To install Node.js it should be as easy as:

sudo apt-get install nodejs
sudo apt-get install npm

Incidentally, rather than using node-sos-device directly, we will be using the higher-level node-sos-client, which knows how to monitor Jenkins and Bamboo CI servers.

Node-sos-client


If you haven't configured your device to work with git you could do it the right way with SSH and generate an ssh key or you could just:

git clone https://github.com/AutomatedArchitecture/node-sos-client.git

and

cd node-sos-client

Next you'll need to download all Node dependencies.  If this is a fresh install you'll need to tell the node package manager (npm) where to retrieve dependencies from:

npm config set registry http://registry.npmjs.org/

Now you can install all dependencies for node-sos-client by running

npm install

Upgrading Node


For some fortunate users (Andy Lowry for one) installing node via apt-get works fine.  If, however, you get an error about node being out of date you'll have to uninstall, download, and update your path.

First, to uninstall the old version of node:

sudo apt-get remove npm
sudo apt-get remove node

No download and unpack:

cd ~
wget http://nodejs.org/dist/v0.10.2/node-v0.10.2-linux-arm-pi.tar.gz
tar -xvzf node-v0.10.2-linux-arm-pi.tar.gz

To add it to your path

nano .bashrc

And add the following two lines at the bottom:

NODE_JS_HOME=/home/pi/node-v0.10.2-linux-arm-pi
PATH=$PATH:$NODE_JS_HOME/bin

If you restart your command prompt and type node --version you should get v0.10.2.

Now retry npm install.

cd node-sos-client
npm install

And you should be good to go.

Running node-sos-client


First make a copy of the default configuration file:

cp config.json.example config.json

We'll configure it correctly later.  Next pick up the dependency on node-sos-device by running:

npm install sos-device

To run the app you should be able to run

sudo node build/sos-client.js

However, if you had to install node with the wget method, then you'll need to run

sudo $NODE_JS_HOME/bin/node build/sos-client.js

If you're lucky you'll see the app print out the device stats as json and a configuration error, something like:

deviceInfo: { version: 1,
  hardwareType: 1,
  hardwareVersion: 1,
  externalMemorySize: 0,
  audioMode: 0,
  audioPlayDuration: 0,
  ledMode: 0,
  ledPlayDuration: 0,
  ledPatterns:
   [ { id: 2, name: 'On/Off' },
     { id: 3, name: 'Fade' },
     { id: 4, name: 'Chase' },
     { id: 5, name: 'Fade Chase' } ],
  audioPatterns:
   [ { id: 1, name: 'Sad Trombone' },
     { id: 2, name: 'Ding!' },
     { id: 3, name: 'Plunk' } ] }
Failed to poll: bamboo0 { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscall: 'getaddrinfo' }

However, if you have a cable that doesn't work well, or are connecting through a non-powered USB hub you may see:

Error: usb_detach_kernel_driver_np: -113 could not detach kernel driver from interface 0: No route to host

In this case try experimenting with the way you connect the device to the Pi.

Configuring the Connection

Today node-sos-client can connect to two CI servers: Bamboo, and Jenkins.  To connect to Jenkins update the config file to something like:

{
  "builds": [
    {
      "type": "jenkins",
      "config": {
        "url": "http://127.0.0.1/jenkins/api/json/",
        "username": "[username]",
        "password": "[password]"
      }
    }
  ]
}

And you're done.  With any luck running sudo node build/sos-client.js will light the siren and sound the speaker on initial connection, and whenever the build breaks.

Summary


And now you too can terrorize your build breaking colleagues, even when you're not at the office.  Enjoy!

Saturday, April 19, 2014

Released 2.2.0

Today we released Siren of Shame 2.2.0, adding some good stuff including the #1 most requested feature:

Custom Audio Sounds 


"Sounds", it's a new option in the menu:


Click it to add/delete/preview MP3's or WAV's:


Then configure rules to play them:


With per-user rules and our fancy rule engine you can now taunt co-workers by name when they break the build.  How cool is that?

Visual Studio Online


If you're into TFS (by choice or divine mandate) and using the Microsoft-hosted cloud version (previously called Team Foundation Services) we now have your back.  See Configuring Visual Studio Online for details.

Keyboard Shortcuts


If you're a keyboard kind of person (and what self-respecting developer isn't?) you'll appreciate the following new keyboard shortcuts:

  • 1-9 - Go to the build detail page for the appropriate build
  • Backspace - Go to the home page
  • Alt+1-9 - Go to the the user detail page for the appropriate user
  • F - Go full-screen

Bug Fixes

  • Can now treat unstable as passing for Jenkins (Issue #30)
  • When new users are added, the leaders tab now immediately updates (Issue #26
  • Fixes an issue with Team City authentication 
  • Fixes a bug with users that have comma's in their user names 
  • Fixes a bug with hidden users 
  • Fixes some issues with build dates (thank you @mightymuke
  • Fixed authentication issues in Travis 
  • Fixed issue #48 typo 
  • Fixed a bug with user mappings (thank you @gregorycu
  • Improved pretty date calculations 

Configuring Visual Studio Online for Siren of Shame

As of Siren of Shame 2.2.0 we now support Visual Studio Online (previously Team Foundation Services).

You will need to configure Visual Studio Online to enable authentication from Siren of Shame.  To do this:

1. Log in to Visual Studio Online
2. Edit your Profile



3. Click Credentials and select "Enable alternate credentials"



4. Enter a username and password
5. When you add a server in Siren of Shame the URL should be https://[myproject]/visualstudio.com/, and the username/password should be what you entered in alternate authentication credentials