NOTE: Links are provided for reference purposes only; no product or vendor endorsement is expressed or implied
- 2 x "SocketRocket" light bulb socket module (LM15A)
- 1 x Transceiver Module (TM751)
- 1 x "Firecracker" Serial Adapter (CM17A)
- 1 x red light bulb
- 1 x green light bulb
- 2 x light bulb socket outlet adapter (something like this)
- 1 x 6-outlet power strip or surge protector (recommend 6 foot cable length)
- CruiseControl with X10 plugin (I believe this was bundled with CruiseControl when I did this)
- Follow "SocketRocket" included directions to assign the two modules different X10 codes (recommend C4 for the red, for humor reasons)
- Set transceiver to a different number on the same letter code used for the "SocketRockets" (might not actually be necessary)
- Screw "SocketRocket" modules into socket outlet adapters
- Screw light bulbs into "SocketRocket" modules
- Hang power strip on wall vertically
- Plug light assemblies and Transceiver directly into power strip, placing red lamp on top and Transceiver on bottom (antenna extended for maximum reception)
- Install "Firecracker" into serial port on CruiseControl server
- Configure CruiseControl build to transmit "on" to the red lamp code and "off" to the green lamp code when build fails, and vice versa when build passes
- First and foremost, I probably wouldn't opt for a lamp setup at all anymore. I usually have more than one build job, and it's important to me to know which ones are in what state, and that is where the lamp paradigm breaks down. My next CI monitoring project will likely use a cheap LCD TV and a RaspberryPi.
- Many machines these days don't have serial ports - the "Firecracker" supposedly works with some USB/Serial adapters, and X10 now make a native USB adapter
- I'd never use CruiseControl for a build anymore, and I'm unsure what other libraries / command line tools exist for X10 automation