27-Jan-2005 Uncategorized

continuous integration

I’ve decided to make a return to Philly for the weekend. I have my dog already checked into the Jersey Village Animal Hospital kennel facility. I was supposed to bring the DeLorean to this Back to the Future Party thing on Friday night. I hate to flake out on them but I’ll make it up to them when the next one rolls around. I get to work out with my trainer on Saturday morning. Good times. The fact that I’m going someplace where the temperature is 15 degrees and there’s a foot or two of snow on the ground doesn’t seem to bother me. As an added bonus, I have not yet been assigned a seat for my return flight on Sunday night. I wonder if I can check in and grab a seat on Saturday at 5 PM, then use that as a bargaining chip to get the coveted ”$300 Travel Voucher” that I prize so highly. I’ll report back from Philly in my next update.


Before I forget… I’ve now turned the theoretical Continuous Integration into reality here at The Office. I have three environments: INTEGRATION, TEST, and PREVIEW. Everytime someone checks in a file to the source repository, CruiseControl.NET detects it and starts a build. If we encounter Yet Another Successful Build after someone checks in some code, everyone with the CruiseControl.NET system tray icon will hear a WAV file of Homer Simpson saying ”Woo hoo!” (if they want). They can also hear about when a build fails (”Doh!”), when it continues to fail (that is, if it continues to fail), and when it succeeds after it had been failing earlier (”Woo hoo!”). Yes, we are easily amused.