CI Hurts!
I've only recently begun working as the Build Czar here at Atalasoft, and immediately there are pains. The builds (from what I see) are really complicated. True: building a very complicated product is going to be complicated; however, it's thought that I can work myself out of this job, making it everyone's responsibility not just one person. How can I do this?
Currently, Atalasoft employs Cruise Control.net, CCTray, NUnit and NAnt to make our CI ship go. Each piece of this puzzle is extraordinarily powerful, the problem is getting them to shine in the way they shine on their own. If I put the pieces in the wrong places, I'm going to overextend one of these applications, and end up paying the price for sure.
Welcome to my blog! For a while I'll be concentrating on overhauling an enterprise build process, the trials, tribulations, pains and glories therein. At then end of this process I can only hope the title and content of my blog will change, as that signals one of two things:
- I accomplished what I set out to do, and the builds are no longer owned by me. My Build Czar title will be retired, and the entire engineering team will work together to ensure the CI process continues.
- The builds break me.
Let's hope it's the former.
Dave Terrell
Build Engineer
