For a while at work, we've been using the Hudson</a> continuous integration server for managing our builds. We use it in a couple different ways.
</div>
</div>
</div>
Hudson
We used to use a home grown solution that was tied very closely with make and specific options being passed, we quickly grew out of this solution.</div>
There have been a couple of hurdles that we've had to overcome, but Hudson is extensible enough that is hasn't been too hard.</div>
Hudson is one of the first open source projects I have contributed to. I wrote a simple plug-in</a> to publish artifacts (things that are created during the builds) to a CIFS share. CIFS, for those of you who may not know, is the file system that Windows uses for sharing directories. So, to make it simple it allows files to be copied to a Windows share from either another Windows machine, or a Linux machine (or anything that jcifs works on). </div></div>
Hudson is really nice. It is very configurable, and really easy to extend to implement what you need it to do. My next job at work is to try out SCons</a> to see if it will work well as a replacement for make.</div>