Essentials of the Build Process


In his CM: the Next Generation series, Joe Farah gives us a glimpse into the trends that CM experts will need to tackle and master based upon industry trends and future technology challenges.

Build is central to CM and iit's critical to do it right. A basic build capability is founded on two key fundamentals: the ability to reproduce the build and the ability to automate the build process. Without these fundamentals, you're fighting an uphill battle. Reproduction of the build implies that you have a CM system able to capture the build definition. Automation helps to ensure that no manual errors can play into the production, but this is just a basic build capability.

Build  is central to CM. It's critical to do it right.

A basic build  capability is founded on 2 key fundamentals:  the ability to reproduce  the build and the ability to automate the build process.  Without these  two fundamentals, you're fighting an uphill battle.  Reproduction of the  build implies that you have a CM system able to capture the build  definition.  Automation helps to ensure that no manual errors can play  into the production.  But this is just a basic build  capability.

To move up the ladder, there's plenty more to be  done.  First of all, automation must be made available to all levels of  the team, from production down to developer.  Each member of the team  needs the same assurance that the right stuff is being built: developer,  integration, verification, production.

It's one thing to automate the build, but in a continuous or regular integration cycle, there could be a lot  of work in deciding what's going into the build, especially in larger  projects.  What is the secret to successful regular builds?  It’s important to make sure that you have quality going into the builds.  To get a series of quality  builds it's important to make sure of 2 things:  start with a stable  build and then ensure that the changes going in are of high quality.

If you have a mediocre build to begin with, don't open the floodgates for  other changes.  First, stabilize the build through intensive debugging and changes that move the quality forward only.  Once you have a stable build, you're in a good position for the second requirement:  high quality  changes.

High Quality Changes
High quality software changes are a product of many factors:

  • Good people
  • Good product architecture
  • Effective peer reviews
  • Feature and integration testing prior to check-in
  • Ensuring the changes that go in are approved

Good people are hard to come by, but good processes, with a good mentor, can make average developers very effective.   A mix of software experience, application experience, objectivity and strong design and software engineering skills are desirable.

Good product architecture is key. In my very first job, I had 1 week to get a code generator debugged and working.  I looked at the architecture and it just wasn't there.   The only way I could make the deadline was to throw out the existing work and rebuild from scratch, although with a good bit of help from the existing work that had been done.  The tactic was successful.  You might not want to throw out your entire flight software or telecom system, but if there are components that are overly complex and lack good architecture, your changes are going to cause problems.  Your builds will have bugs that need to be ironed out before restoring a stable build, which is the first premise for the next build.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.