bencarey's dashboard

That's great. Thanks for the help there.

I think XmlStatusReport.aspx is only exposed from .rb and CCNet and that it's a different url for the java cruise. My code changes that in the trunk right now break on anything that doesn't expose XmlStatusReport.aspx (at least if you use the settings dialog instead of the config file) because of a converter I added for usability-sake.

Overall, I'd like to keep it where you never have to specify which version of cruise is running on either end. Overall, it really shouldn't matter as long as the xml exposed is consistent. As far as I know, this is currently the case. – bencarey, on June 03, 2008 10:55

Sounds good. I'm updating the code fairly frequently right now, but mostly just trying new stuff out.

I also want to write a "hand-drawn" visualization and then do some cleanup and announce 1.0 (likely by the end of next week). – bencarey, on May 30, 2008 14:14

I'm not sure what that error message would be. I just pulled over a different machine, downloaded tortoise and did a checkout with the command above and it seemed to work fine (with http://bigvisiblecruise.googlecode.co...).

Regarding showing the last user that committed a change, we use this information, but we just use the information from cctray. So, we use BVC simply for big visibility and cctray when we need more information.

Maybe the best way to have access to see the last checkout is simply to launch the dashboard from one of the build blocks that are show in the visualization.

I'd like to see that as well. The issue currently is that the xml that is returned from the cruise instance doesn't provide this information. It's possible to get this from the remoting endpoint in CCNet, but as far as I'm aware, this isn't available from the other cruise implementations (non-.Net).

I'll dig into this a bit and see what else I can find. This feature has been requested before.

As far as the url goes to the repo, it's a command-line url that google publishes. It should be fine from the commandline. If you're using tortoise, use http://bigvisiblecruise.googlecode.co....

I'll reply to my own post and let you know how we use it at my company right now...

We have 3 dedicated monitors that are always on. We have 3 of the 4 corners of the room showing the visualizations on dedicated monitors. This allows for anyone to look up from their monitor and see what the current status of each build is.

In addition to BVC, we also have CCTray running to give us auditory alerts to the build status.

Having the monitors displayed prominently around the room allows for everyone to know the status of the build as soon as they walk in the room and for others to know the status of the build as they visit our team room.