Real quickly, check out our brand spanking new build server. Notice anything different? No? Good! Hopefully everything is working just fine, but faster. As you know, I’m ever the optimist. What’s that trite phrase, “When the crap hits the fan, make lemonade”? Or something like that. So in this tragedy becomes triumph story, the bricking of my tiny little home built build server caused me to start thinking of a more permanent solution. In steps Eric Kemp, Rob Conery’s right hand man (in the clean sense of the idiom) on the Subsonic team. He converted the VMWare image to run on...
Not too long ago I mentioned that a power surge bricked the Subtext Build Server. What followed was a comedy of errors on my part in trying to get this sucker back to life. Let my sleep deprived misadventures be a cautionary tale for you. My first assumption was that the hard drive failed, so I ordered a new Hard Drive. Lesson #1: If you think your hard drive has failed, it might not be a bad idea to actually test it if you can. Don’t just order a new one! I have my main desktop machine I could...
Simone Chiaretta, a member of the Subtext team (not to mention many other projects), just released a Vista Gadget which allows you to monitor a CruiseControl.NET build within your sidebar. It looks spiffier than the system tray applet that comes with CCNET. Here’s a screenshot of it docked. And undocked. From the screenshots you can see the status of the projects he is monitoring. The good news is that the 1.9 build has been fixed since he took these screenshots. Pretty nifty! Technorati tags: Vista, Gadget, CCNET, CruiseControl.NET, Build Process
I’m not proud of it (well maybe just a little), but I once created an insane build process once. If Pat (who maintained the build after me) posts in my comments, he’ll tell you about it. Take a stew of a proprietary microcomputer flavor of Fortran written in the 70s by a programmer most assuredly clad in polyester, churn it through a Visual Basic 6.0 preprocessor that spits out Fortran 90 code, all the while correcting memory bound issues, mix it together by compiling it with a custom NAnt fortran compiler task, and voila!, 20 or so compiled Win32 fortran...