This chapter completes our discussions of an integrated and automated software build and release life cycle solution. I hope by now you agree that there is more to Software Build and Release Management than at first it seems and that there are significant benefits to be had from implementing the "right" process. The question, however, is just what the "right" process is. Well, in this chapter I have given you some ideas and starting points, concluding with an example of how a complete end-to-end software build and release process could be implemented. However, if I had to identify just three imperatives to set you on your way, they would be as follows:
I have spent a considerable amount of time in this book discussing the technical implementation of a specific set of toolsnotably, ClearCase, Ant, and CruiseControldescribing how they can best be implemented both as individual products and when integrated. Hopefully, this will set you on your way to mastering them. Remember, however, that any software build and release process is of no benefit in isolation. Rather, it is there to support any overriding software development and deployment process. Identifying your project rhythm as described in this chapter is a mechanism I believe you can use to help identify how the way you build and release can directly support this overriding process. If you can build better, faster, and with more confidence, you will ultimately be on the right path to increasing your project's productivity, traceability, and efficiency.