This morning I came across a blog by Landon Dyer called Dadhacker. He got linked by BoingBoing for a entertaining post that he wrote about working on the Donkey Kong cartridge for Atari. I started reading his other posts and it turns out that I agree with nearly all of his opinions. Except for build boxes. He wrote:
The best thing you can do for your productivity when you’re tempted to set up that spare machine to do extra work for you is to ditch the thing.
If you are the person only using that build machine, I can see that point. Almost. I would argue that it’s worth the time to have a 2nd machine in case the first one goes to the land whre DOS is eternally blessed. For a team of programmers, having a dedicated build box is a must have feature. No more guessing which program set which option to build which executable, they always get built the same way. Plus it offloads the build process processing from your development environment and that is always a good thing.
The other advantage to having a dedicated build box is that you have have it do everything. We use FinalBuilder and it’s the kitchen sink of automated build tools. We build about a half dozen or so shrink wrap ready applications on our build box and they all pretty much follow the same pattern:
- Get the latest code from source control
- Read an .ini to get the version number and other test resources, the build tool will bake the version number into the compiler and install builder.
- Compile the application
- Collect all of the bits and put them in a folder for the install builder
- Authenticode anything remotely executable that we compiled
- Create the installer from all bits that were compiled in the last step and add the necessary required bits (CaptiveX controls, Assemblies, help files, etc).
- Copy the installer to a deployment folder for QA to test
- Send an email to QA and other interested parties that a new build was available and include a change list in the email.
There are other minor tasks that get performed, but that’s the gist of it. And it works for for Delphi Win32 and .NET assemblies, with error handling. The time our department saves that level of build automation clearly outweighs the the maintenance time on the build box.