Comments on: 6 Big Visible Continuous Integration Tools

By: Julian Simpson

Julian Simpson — Mon, 19 Jul 2010 21:22:21 +0000

Thanks Rene, I’ve updated the list – and discovered that there’s quite a few to look at …

By: Rene Medellin

Rene Medellin — Mon, 19 Jul 2010 12:56:20 +0000

Brand new-ish Wallboards for JIRA (fetching information from your Bamboo build agents but should be able to work with other CI servers as well)

http://blogs.atlassian.com/developer/2010/06/wa...

By: David Ron

David Ron — Tue, 22 Jun 2010 02:04:21 +0000

Also, check out Big Visible Cruise Web, a clone of Big Visible Cruise that runs in the web browser:

http://code.google.com/p/big-visible-cuise-web/

By: James Summerton

James Summerton — Fri, 11 Dec 2009 01:31:57 +0000

Another plug

Check out Cradiator (http://cradiator.codeplex.com/) a fork of BigVisibleCruise with a load of enhancements.

It has full support for CruiseControl (Java, .NET, Ruby) and now TeamCity as well.

Some of the key new features:

* Shows breakers of a build (if broken) or the volunteer to fix the build (for CCNet requires 1.4.3 or greater)
* New skin (StackPhoto)
* Filter by Category (in addition to Project Name)
* Show progress/status when making connection to Cruise server (configurable)
* Color gradients for visual appeal
* Wav files can be played on specific events (currently ‘NewlyBrokenBuild’ and ‘NewlyFixedBuild’)
* Speech synthesis – Cradiator says which build is broken (handy for those with sore necks who can’t check the big screen) – uses SAPI support on Windows. The text to say and the voice itself is configurable – so you can Download your own voices
* Show a Countdown of how many seconds to go before refreshing status
* Added a Debug-mode facility to allow developers to replace the Cruise Web Service XML with their own XML – handy for UI testing/experimentation and screenshot/demos
* Configuration changes:

1. An app restart is not required for settings to take effect
2. Config file can even be edited while the app is running (ie is ‘watched’ for changes and applied immediately or at the next refresh interval)

* Settings dialog (for people with text-editor phobias)
* Logging (using log4net) – can be configured via app.config

By: paulgreg

paulgreg — Tue, 25 Aug 2009 09:24:23 +0000

I've built another system composed of 2 parts : - the "green/red screen" : http://build-status.appspot.com/ - and a "trigger", currently only for TeamCity (but you can easily develop your own trigger according your build system) For now, a big limitation about the "screen" is that it's only display 1 project at a time (I've planned to fix that limitation in the future).

By: Carlos Villela

Carlos Villela — Wed, 19 Aug 2009 03:51:36 +0000

Blatantly shameless plug: I have built a couple of radiators using Quartz Composer (Mac-only, unfortunately) and created a template so you can build your own:

http://www.lixo.org/archives/2008/07/05/information-radiator-screen-savers-for-macos-x

It’s by no means “complete”, but I would definitely welcome some help, seeing I don’t have much time to mess with it, or that much experience with Quartz Composer.

By: Jeffrey Fredrick

Jeffrey Fredrick — Tue, 18 Aug 2009 23:25:02 +0000

Cool to see all these tools out there. Back at Agitar we tried a bunch of different approaches; lava lamps remain my favorite. (The ambient orb looked cool but was kind of a dud in practice.) Anyone looking to find more can try searching on "extreme feedback device".

By: Sidu

Sidu — Tue, 18 Aug 2009 21:21:24 +0000

Back in the day (~2004), JD (http://robotics.usc.edu/~jnaneshd/pmwiki.php) used to put together a custom build tower using ruby scripts, aluminium struts and LEDs. One level of the tower would light up for every stage of the build that passed.

I don’t think we have an pictures though, more’s the pity.