What have you done? I wrote a Build Radiator, or eXtreme Feedback Device.
Not another one! Why?
A few weeks ago, someone quite innocently locked their Continuous Integration server. They locked it so hard, it caused the threads that listen for incoming TCP connections to lock up. This quietly removed their Build Radiator and Continuous Integration server UI from the network. Such an event causes great hilarity, as it causes developers to think that there’s a network issue, and ask the wrong people to help fix the Continuous Integration server.
What caused the problem was a slightly mangled version of a plugin that creates a Build Radiator. The product in question is fine. The outage did cause me to reflect on scaling Continuous Integration, however. As we scale up development teams, when should we stop dicking about with the server? How do you expose the state of the build if you keep your mitts off it?
So I set out to build an eXtreme Feedback Device that had no dependencies, and no need to deploy. The first version is below. It supports Hudson right now, and I plan to add support for more Continuous Integration servers in the future..
What’s next? I’m going to add JSONP support to a Continuous Integration server. We’d also like your feedback. I’d like to add some more information to it: for example, it would be nice to be able to tell you there’s a new version of this tool, or perhaps your CI server.
Are there others? Yes.