Recommendations


  • Create the mainline (public) and virtual build labs (private) codelines.

  • Make sure the mainline is pristine and always buildable and consumable. Create shippable bits on a daily basis. Use consistent, reliable builds.

  • Build private branches in parallel with the main build at a frequency set by the CBT.

  • Use consistent reverse and forward integration criteria across teams.

  • Be aware that dev check-ins are normally made only into a private branch or tree, not the mainline.

  • Know that check-ins into a private branch are only reverse integrated (RId) into main when stringent, division-wide criteria are met.

  • Use atomic check-ins (RI) from private into main. Atomic means all or nothing. You can back out changes if needed.

  • Make project teams accountable for their check-ins, and empower them to control their build process with help from the CBT.

  • Configure the public/private source so that multisite or parallel development works.

  • Optimize the source tree or branch structure so that you have only one branch per component of your product.



The Build Master(c) Microsoft's Software Configuration Management Best Practices
The Build Master: Microsofts Software Configuration Management Best Practices
ISBN: 0321332059
EAN: 2147483647
Year: 2006
Pages: 186

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net