I'd want to be notified of a complete build failure but not necessarily a partial one because it might be a while before it's fixed, which means every build will trigger a notification and become simply noise. I would want a notification when build quality worsens, though.

I build was broken and displayed as such.

The next action then was - someone tried to fix it and then started a build. They then had a change of heart, having thought of something and cancelled the build.

The dashboard icon for the individual build should change from the white arrow on green (running/queued build) to a new icon for cancelled. The overall status of the build definition should be taken from the last completed build and should not remain as running, so in this case should change from the large green arrow to the white cross in a red circle.

https://github.com/drone/drone

Probably, the easiest way is to add support for cctray xml format.

See https://github.com/robertmaldon/cc_dashboard#cctray-xml-format

http://ccmenu.org works with any compatible CI.

Just downloaded your application and I'm really impressed.  It works really well.  I'm currently working on some continuous deployment stuff for the company I work at and specifically running scripts on a local machine as a result of a particular build succeeding, failing etc.

It would be really awesome to be able to leverage all of the polling and notification stuff that you guys are already doing and be able to react to certain events (i.e. run a script when Project A succeeds -> passing in build context perhaps to the script).

Embrava Connect is a small device which can be connected through USB. It ships with a small SDK. The cool part is that it has a full RGB light and optionally a little speaker which can be used as a build notification light. The SDK is available for .NET.

Would be great if either:

 * Catlight would provide direct integration with Embrava Connect

 * Catlight would offer an extension API which would allow us to react on status changes

http://www.embrava.com/pages/software

This will make it useful on a team where not everyone is using the app.

Hi Guys

I would love to see a setting that you could add a Siren sound to a build failure notification. I really wanted to install this on the computer that is connected to our projector and have the entire team informed when a build fails!! This would be great.

Cheers Joe.

When build succeed, I want to go directly to console page for the artificial.

When build failed, I want to go directly to console page for error checking.

So it will be great to have a way to jump there!

Is it me or is the catlight icon very similar to that of github? This is especially true when its a small icon in the taskbar.

In TFS, and I suppose other build system have this too, I can do a gated check-in. That is make the server build a shelfset that is not checked in to any branches yet. If the build succeeds, the changes will be checked in, if it fails, nothing will be checked in.

If the build of such a gated check-in fails the cat should not become red.

Submitted by: bit bonk.

It would be nice if it was possible to organize the dashboard such that the hierarchy was: Team > Project > CI Provider, instead of CI Provider > Team > Project, as it is now.

Since all projects I have in CatLight are on GitHub, it feels more natural to organize them from a GitHub perspective, where which CI servproviderce builds the project is secondary to the team and project/repository.

With such an organization of the dashboard, each CI provider could be represented with nothing more than a logo with a traffic light beside it, to indicate the build status of the associated

Please add support for CruiseControl.Net (http://www.cruisecontrolnet.org/projects/ccnet)

The Travis Support is cool... can we add Travis Enterprise support?  I think it is basically the same except that the URL will be different.

Catlight should support the Harbormaster build server that is part of Phabricator.

To receive the status of builds within Harbormaster, you'll need to get the user to provide an API token.  Once you have that, you can query the API endpoints in Conduit to find out:

• A list of repositories the user has access to: https://secure.phabricator.com/conduit/method/diffusion.repository.search/
• A list of branches in each repository: https://secure.phabricator.com/conduit/method/diffusion.branchquery/
• With the commit hashes, you then need find out the internal PHIDs (unique identifiers) of those commits with: https://secure.phabricator.com/conduit/method/diffusion.querycommits/ 
• Then you can query the pass / fail status of those commits by passing those PHIDs in as "buildablePHIDs"