Cradiator

Commented Issue: foresee a skin that is easier to read when you have many projects [464]

stevedonie — Mon, 01 Mar 2010 20:49:34 GMT

I would go for a screen like following
Ok Projetcs | Broken projects
name name

the OK and Broken projects have their own list, placed inside a grid or so
give the projects about 30% of the width of the screen, and the Broken ones 70%
so these stand out more
I have 45 projects to monitor, and now the size of the individual projects is to small.
and I am only intrested in the broken ones, these have to stand out, the ok ones in the green may be smaller, they do not need attention
Comments: ** Comment from web user: stevedonie **

Very similar to issue 3488
http://cradiator.codeplex.com/WorkItem/View.aspx?WorkItemId=3488

New Post: Cradiator Improvements

PandaWood — Tue, 16 Feb 2010 23:09:08 GMT

Hi Piffie, Thanks. The best way to send code to me is to create a "patch" - which you can create using TortoiseSVN (How to create a patch)

Don't worry about comments too much - more important is that the code is clear, and you can usually do that just be writing the code in a certain way.

New Post: Cradiator Improvements

piffie — Tue, 16 Feb 2010 15:18:14 GMT

Hi,

as i'm starting again on using the cradiator in our company, i did do some enhancements.

1) i added a ProjectImportance to the ProjectStatus object, returning 3 for currently building, 2 for broke, 1 for OK.
gives me a sort ordering for the result window.

2) added a limitation to the display.
currently i limit it hardcoded to the ScreenUpdater class, but i would add it in the config later.

if you want, i can add that code (and for sure commeted) to the codebase,

or you can do it by yourself.

expect definitly more to come.

thanks for that great work.

cheers,

christoph

Source code checked in, #39403

PandaWood — Sun, 14 Feb 2010 23:36:29 GMT

orders the breakers in order of who broke it (so Cradiator can properly use the show-first or show-last strategy)

Closed Issue: Countdown to Release Day [2698]

PandaWood — Thu, 03 Dec 2009 06:57:14 GMT

I would like to see a countdown to release day added to the bottom with the option to replace the countdown to refresh with a weeks, days,hours, minutes, seconds countdown to the release

I always either release on the monday after the 1st or 15th every 6 weeks. And it would be good to know how much time my team has till we release

Updated Release: Cradiator v2.6 (The Watermelon Release) (Jun 08, 2009)

PandaWood — Thu, 03 Dec 2009 06:46:06 GMT

Cradiator has a new name (previously BigVisibleCruise2). This new release includes some touch ups and essentials for voice synthesis, config and showing progress during network activity.

I modified the 2.5x release to become 2.6 It contains 1 extra feature (see bottom of list below). Apart from new skins, I think most of the functionality of Cradiator is now done. So I wanted to get a release out to coincide with this.

New

Voice Name used in speech synthesis is configurable - see SpeechVoiceName. The voice name does not have to be exactly correct, for example william is close enough to select the Cepstral William voice. If the name is ambiguous then the first matching name, in alphabetical order, will be selected
Filter by Category - using configuration property CategoryRegEx. This filter is in addition to filtering by project name ProjectNameRegEx. The default Regex is ".*" - even if an empty string is set. Must edit config file directly for this - not added to the Settings Dialog
Added more config settings to the Settings Dialog. Previously, many settings required config file editing
Removed the assumption http:// at the beginning of the URL (to cater for https)
Progress bar - the data fetch is now performed on a separate thread so progress can be shown on the main screen (if configured) in the form of an "indeterminate" progress indicator. This is useful for getting some visual indication of when the update has happened
Variables can now be used in the speech text (FixedBuildText and BrokenBuildText) eg BrokenBuildText="$ProjectName$ is broken, $Breaker$, you're fired!"
"Real Names" can be specified for usernames (in config) so that unpronounceable usernames can be spoken by the speech synthesizer - eg jsmith can be configured to be spoken as "John Smith" - see usernames section in the configuration file (eg <usernames> <add key="jsmith" value="John Smith"/> </usernames>)
Change the strategy used to determine the BuildBreaker (First/Last) - does the First breaker stay guilty or do subsequent comitters take on the responsibility

Under The Hood

Refactoring of Converters (and deletion of some that were unused) to use the DI mechanism to resolve their dependencies (by use of MarkupExtensions)
Refactored XAML to use more styles and less repetition
Work on main screen layout for flexibility in positioning

NB This release is not compatible with the XML format changes made in CCnet 1.5

Released: Cradiator v2.6 (The Watermelon Release) (Jun 08, 2009)

Thu, 03 Dec 2009 06:46:06 GMT

New

Voice Name used in speech synthesis is configurable - see SpeechVoiceName. The voice name does not have to be exactly correct, for example william is close enough to select the Cepstral William voice. If the name is ambiguous then the first matching name, in alphabetical order, will be selected
Filter by Category - using configuration property CategoryRegEx. This filter is in addition to filtering by project name ProjectNameRegEx. The default Regex is ".*" - even if an empty string is set. Must edit config file directly for this - not added to the Settings Dialog
Added more config settings to the Settings Dialog. Previously, many settings required config file editing
Removed the assumption http:// at the beginning of the URL (to cater for https)
Progress bar - the data fetch is now performed on a separate thread so progress can be shown on the main screen (if configured) in the form of an "indeterminate" progress indicator. This is useful for getting some visual indication of when the update has happened
Variables can now be used in the speech text (FixedBuildText and BrokenBuildText) eg BrokenBuildText="$ProjectName$ is broken, $Breaker$, you're fired!"
"Real Names" can be specified for usernames (in config) so that unpronounceable usernames can be spoken by the speech synthesizer - eg jsmith can be configured to be spoken as "John Smith" - see usernames section in the configuration file (eg <usernames> <add key="jsmith" value="John Smith"/> </usernames>)
Change the strategy used to determine the BuildBreaker (First/Last) - does the First breaker stay guilty or do subsequent comitters take on the responsibility

Under The Hood

Refactoring of Converters (and deletion of some that were unused) to use the DI mechanism to resolve their dependencies (by use of MarkupExtensions)
Refactored XAML to use more styles and less repetition
Work on main screen layout for flexibility in positioning

NB This release is not compatible with the XML format changes made in CCnet 1.5

Updated Wiki: Home

PandaWood — Thu, 03 Dec 2009 06:43:59 GMT

Cradiator is a Windows (WPF) app that displays a summary of Continuous Integration (CI) project statuses. It is basically an Information Radiator for CI. Cradiator currently supports Cruise Control (Java, .Net, Ruby) and Team City (using our Cradiator TeamCity plugin)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success/Normal
Red	Failure/Exception/Error
Yellow	Building
White	Unknown

Cradiator is a continuation (or "fork") of Ben Carey's BigVisibleCruise at GoogleCode.
NB all the important features below were added to Cradiator and are not found in BigVisibleCruise. The conversion to Cradiator also included a significant refactoring - extreme separation of concerns (SRP), reduction of assemblies, C#3 features etc

Important 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:

An app restart is not required for settings to take effect
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

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Wed, 02 Dec 2009 11:47:15 GMT

Cradiator is a Windows (WPF) app that displays a summary of Continuous Integration (CI) project statuses. It is basically an Information Radiator for CI.
Cradiator currently supports Cruise Control (Java, .Net, Ruby) and Team City (using our Cradiator TeamCity plugin)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success/Normal
Red	Failure/Exception/Error
Yellow	Building
White	Unknown

Important 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:

An app restart is not required for settings to take effect
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

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Wed, 02 Dec 2009 03:32:15 GMT

Cradiator is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and TeamCity (with plugin included)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Important 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:

An app restart is not required for settings to take effect
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

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Wed, 02 Dec 2009 03:31:09 GMT

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Important Features

Shows CurrentMessage - which is the 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:

An app restart is not required for settings to take effect
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

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Source code checked in, #32610

PandaWood — Wed, 02 Dec 2009 03:28:18 GMT

added TeamCity plugin stuff

Created Issue: Multiple Refresh intervals - one for building and one for sleeping [3493]

demyte — Mon, 30 Nov 2009 04:36:49 GMT

It would be good for there to be two intervals for refresh, one that is active when a project is building and another for when no projects are building.

e.g.

Building Refresh = 5
Sleeping Refresh = 30

This makes it so when no projects are building, Cradiator goes into a 30sec refresh interval, but when it detects a project is building, it brings the poll interval down to 5 seconds so if there is a failure there is immediate feedback to the room.

Created Issue: MODE: Only show broken [3488]

demyte — Sat, 28 Nov 2009 09:58:36 GMT

I would like to have a mode you can enable where only broken projects are shown on the display.

If there are no broken projects, a nice default screen can be displayed with a message saying everything is OK. This message could be configurable.

Maybe worthwhile to extend this to a mode "Only Show... " and then select the modes to show using checkboxes, i.e. Broken Building Unknown Successful All

Updated Wiki: Home

PandaWood — Fri, 27 Nov 2009 17:33:01 GMT

Cradiator is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and we've just created a plugin for TeamCity to create output that Cradiator can read (to be included shortly)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Important Features

Shows CurrentMessage - which is the 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:

An app restart is not required for settings to take effect
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

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Fri, 27 Nov 2009 17:29:17 GMT

Cradiator is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and we've just created a plugin for TeamCity to create output that Cradiator can read (to be included shortly)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Cradiator is a continuation (or "fork") of Ben Carey's BigVisibleCruise at GoogleCode. NB all the important features below were added to Cradiator and are not found in BigVisibleCruise.

Important Features

Shows CurrentMessage - which is the 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:

restart no longer required for settings to take effect
Config file can be edited while the app is running (ie is 'watched' for changes and applied immediately or at the next refresh interval)
Names simplified (eg "30" instead of "00:00:30" for Poll Frequency "Grid" instead of "LiveUniformStatus")

Fixed TODO issues - such as the small memory leak with application resources
Usability enhancements to Settings dialog (positioning/text/look/feel etc)
Logging is implemented (using log4net) - can be configured via app.config
More exceptions are handled to protect developers from obscure messages (and they're logged)
Refactoring - design changes, extreme separation of concerns (SRP), reduction of assemblies, C#3 features

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Fri, 27 Nov 2009 17:27:06 GMT

Cradiator is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and we've just created a plugin for TeamCity to create output that Cradiator can read (to be included shortly)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Cradiator is a continuation (or "fork") of Ben Carey's BigVisibleCruise at GoogleCode. NB all the important features below were added to Cradiator and are not found in BigVisibleCruise.

Important Features

Shows CurrentMessage - which is the 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:
restart no longer required for settings to take effect
Config file can be edited while the app is running (ie is 'watched' for changes and applied immediately or at the next refresh interval)
Names simplified (eg "30" instead of "00:00:30" for Poll Frequency "Grid" instead of "LiveUniformStatus")
Fixed TODO issues - such as the small memory leak with application resources
Usability enhancements to Settings dialog (positioning/text/look/feel etc)
Logging is implemented (using log4net) - can be configured via app.config
More exceptions are handled to protect developers from obscure messages (and they're logged)
Refactoring - design changes, extreme separation of concerns (SRP), reduction of assemblies, C#3 features

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Fri, 27 Nov 2009 17:21:53 GMT

Cradiator is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and we've just created a plugin for TeamCity to create output that Cradiator can read (to be included shortly)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Cradiator is a continuation (or "fork") of Ben Carey's BigVisibleCruise at GoogleCode

What's new in in Cradiator

Added showing of CurrentMessage - which is the breakers of a build (if broken) or the volunteer to fix the build (for CCNet requires 1.4.3 or greater)
Added a 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:

restart no longer required for settings to take effect
Config file can be edited while the app is running (ie is 'watched' for changes and applied immediately or at the next refresh interval)
Names simplified (eg "30" instead of "00:00:30" for Poll Frequency "Grid" instead of "LiveUniformStatus")

Fixed TODO issues - such as the small memory leak with application resources
Usability enhancements to Settings dialog (positioning/text/look/feel etc)
Logging is implemented (using log4net) - can be configured via app.config
More exceptions are handled to protect developers from obscure messages (and they're logged)
Refactoring - design changes, extreme separation of concerns (SRP), reduction of assemblies, C#3 features

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Fri, 27 Nov 2009 17:21:07 GMT

Cradiator (formerly BigVisibleCruise2) is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and we've just created a plugin for TeamCity to create output that Cradiator can read (to be included shortly)

Cradiator is most suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Cradiator is a continuation (or "fork") of Ben Carey's BigVisibleCruise at GoogleCode

What's new in in Cradiator

Added showing of CurrentMessage - which is the breakers of a build (if broken) or the volunteer to fix the build (for CCNet requires 1.4.3 or greater)
Added a 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:

restart no longer required for settings to take effect
Config file can be edited while the app is running (ie is 'watched' for changes and applied immediately or at the next refresh interval)
Names simplified (eg "30" instead of "00:00:30" for Poll Frequency "Grid" instead of "LiveUniformStatus")

Fixed TODO issues - such as the small memory leak with application resources
Usability enhancements to Settings dialog (positioning/text/look/feel etc)
Logging is implemented (using log4net) - can be configured via app.config
More exceptions are handled to protect developers from obscure messages (and they're logged)
Refactoring - design changes, extreme separation of concerns (SRP), reduction of assemblies, C#3 features

Cradiator requires .Net3.5 installed (currently no check for this in the installer)

Updated Wiki: Home

PandaWood — Fri, 27 Nov 2009 17:20:16 GMT

Cradiator (formerly BigVisibleCruise2) is a Windows app that displays a summary of Continuous Integration (CI) eg Cruise Control project statuses.
It is basically an Information Radiator for CI - currently supports Cruise Control (all implementations - Java, .Net, .rb) and we've just created a plugin for TeamCity to create output that Cradiator can read (to be included shortly)

Cradiator is well suited to display on a dedicated monitor where it is visible to developers working on a project.
There are various screen layouts or skins to choose from:

Stack Skin

Also showing is a countdown of how many seconds to go before refreshing (shown here as "00:03") - this can be switched off.

Grid Skin

StackPhoto Skin

Shows an image alongside a broken project (based on the breaker's username). Only 1 breaker is shown.

Color Chart

Color	Status
Green	Success
Red	Broken (Failure or Exception)
Yellow	Building
White	Unknown

Cradiator is a continuation (or "fork") of Ben Carey's BigVisibleCruise at GoogleCode

What's new in in Cradiator

Added showing of CurrentMessage - which is the breakers of a build (if broken) or the volunteer to fix the build (for CCNet requires 1.4.3 or greater)
Added a 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:

restart no longer required for settings to take effect
Config file can be edited while the app is running (ie is 'watched' for changes and applied immediately or at the next refresh interval)
Names simplified (eg "30" instead of "00:00:30" for Poll Frequency "Grid" instead of "LiveUniformStatus")

Fixed TODO issues - such as the small memory leak with application resources
Usability enhancements to Settings dialog (positioning/text/look/feel etc)
Logging is implemented (using log4net) - can be configured via app.config
More exceptions are handled to protect developers from obscure messages (and they're logged)
Refactoring - design changes, extreme separation of concerns (SRP), reduction of assemblies, C#3 features

Cradiator requires .Net3.5 installed (currently no check for this in the installer)