A formal build-and-deploy process becomes essential.

2007-12-06

    I’m reading Pro BizTalk 2006 by Apress and a section in the chapter about setting up a new BizTalk project made me a little upset.

    The author thinks it is a disadvantage that: ‘A formal build-and-deploy process becomes essential.

    WTF; in an organization big enough to think about, and afford, BizTalk I would say that a formal build-and-deploy process is a prerequisite. Since BizTalk is a lot, if not all, about integrating different systems and organizations having a strict configuration management is essential to keep the cost down and the quality up.

    It is a nightmare to find, and correct, errors that exists because there is version inconsistency between the partners in an integration project. I find that having a formal build-and-deploy process is almost essential even for a small one man project. I’d even say it’s more important the more infrequent there is work done on a small project.

    On a software project, of any kind, there has to be a formal build-and-deploy process in place as soon as there is artifacts to be delivered from a developer.