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)