book

Build Master, The: Microsoft’s Software Configuration Management Best Practices

Name: Build Master, The: Microsoft’s Software Configuration Management Best Practices
Author: Vincent Maraia
ISBN: 0321332059

by Vincent Maraia

September 2005

Intermediate to advanced

288 pages

5h 57m

English

Addison-Wesley Professional

Read now

Unlock full access

Copyright
Dedication
Praise for The Build Master
Foreword
Preface
What This Book Is AboutDefining Software Configuration ManagementWho Should Read This BookInformation Technology (IT) ManagersSoftware Development and Testing ManagersBuild Teams and Build ManagersTechnical Project and Product ManagersAnyone Interested in a Microsoft Case StudyAssumptions Made on the Background of People Reading This BookHow This Book Is OrganizedContents at a GlanceThe StoryGet Stuck or Get Results. Period.OutsourcingWhat This Book Is Not About: Software FactoriesUpdates and Contact Information
About the Author
In Appreciation and Acknowledgment
Introduction
What “NT” Really Stands ForHow MSN Builds Code
1. Defining a Build
The Two Types of Builds: Developers and ProjectBuilding from the Inside OutMore Important Build DefinitionsHow Your Product Should FlowSoftware Development FlowSome Work Item Field DefinitionsWAR or Ship MeetingRelease to Staging ServersImportant DefinitionsSolution FilesProjectMicrosoft Solution FrameworkSummaryRecommendations
2. Source Tree Configuration for Multiple Sites and Parallel (Multi-Version) Development Work
DefinitionsHow This Process Works: An Example Using VSSGolden Tree (Mainline “Pristine” Build) SetupVBLs and Multisite DevelopmentWhat Should Be Kept Under Source ControlHatteras: A Look Into the Future of SCC at MicrosoftMerging Functionality in TFSCHow TFSC Addresses the ScenariosBranching in TFSCRelease BranchingPromotion ModelingDeveloper IsolationLabel BranchingComponent BranchingPartial BranchingIdentifying Branches (Configurations)More ScenariosShelving Current ChangesOffline Checkout/Check-InSummaryRecommendations
3. Daily, Not Nightly, Builds
The Importance of a Successful Daily BuildHow to Successfully Release Builds and Police Build BreaksBuild Breaks Always Have the Highest Priority for EveryoneEnforce All Build Policies on ReviewsWhat Are You Building Every Day?SummaryRecommendations

4. The Build Lab and Personnel
The Need for a Build LabBuild Lab RulesHardware ConfigurationHardware RequirementsSet Up the SoftwareSet Up the Operating SystemSet Up the ApplicationsSet Up the Build Environment for the Build MachinesBuild PersonnelSummaryRecommendations
5. Build Tools and Technologies
First, Every Build Needs a ScriptBinary Generating Tools—Also Referred to Loosely as “Build Tools”“You Provide the Nose; We Provide the Grindstone”Make or NMakeANT or NANTIn Steps the 800-Pound Gorilla!XML Is the Here, the Now, and the FutureWhat Build Tool Should You Be Using and When?SummaryRecommendations
6. SNAP Builds—aka Integration Builds
What Is a SNAP Build?When to Use SNAP BuildsHow SNAP WorksSample Machine ConfigurationOperations StaffManaging ThroughputSummaryRecommendations
7. The Build Environment
Setting Up the EnvironmentSetting Up a Developer or Tester MachineA Makefile Example That Explains How This WorksSummaryRecommendations
8. Versioning
Why Worry About Versioning?File VersioningBuild NumberSource Code Control TreesShould There Be Other Fields in the File Version Number?DLL or Executable Versions for .NET (Assembly Versions)How Versioning Affects SetupInstall the Correct Version of a Component for the Operating System and LocaleWrite Components to the Right PlacesDo Not Install Older Components Over Newer Ones”Copy on Reboot” If Component Is in UseRegister Components Correctly; Take Security into AccountCopy Any Component That You OverwriteRedistribute a Self-Extracting EXE Rather Than Raw ComponentsTest Setup on Real-World SystemsEven Installing Correctly Does Not Always WorkSummaryRecommendations
9. Build Security
Physical Security for the Build, Source, and Release LabTracking Source Changes (All Check-Ins)—The Build ProcessBinary/Release Bits AssuranceIT InfrastructureWant More Security?SummaryRecommendations
10. Building Managed Code
The Official Definition of Managed CodeWhat Is the CLR, and How Does It Relate to Managed Code?Managed Execution ProcessThe Definition of Assemblies As It Pertains to the .NET FrameworkDelay Signing and When to Use ItThe Problem with This CommandProtecting Yourself from the Security Hole You Just CreatedOne Solution or Many Solution Files?SummaryRecommendations
11. International Builds
Important Concepts and DefinitionsMethod 1: Internationally Ignorant CodeMethod 2: Locale-Dependent SourceMethod 3: Single Worldwide SourceMethod 4: Single Worldwide BinaryUSE UnicodeSummaryRecommendations
12. Build Verification Tests and Smoke Tests
Smoke TestBuild Verification TestsDefine the Scope or Span of the BVTsBVT StatesSummaryRecommendations
13. Building Setup
The Basic DefinitionsSetup Is Not a Testing ToolSummaryRecommendations
14. Ship It!
Software Release at MicrosoftSummaryRecommendations
15. Customer Service and Support
Goals of SupportHow Support Works and Communicates with the Product TeamsSummaryRecommendations
16. Managing Hotfixes and Service Packs
Introduction to “Release Management with VSS”ToolsVersioningVersioning in .NET CodeVersioning in Source ControlRelease Management: General ScenariosPrimary ReleasesShare and PinBranchLabelClonePatch Releases (Service Packs)MergeOther ApproachesParallel ReleasesSummaryRecommendations
17. 7 Suggestions to Change Your Corporate or Group Culture
What Is Corporate Culture?It Starts at the TopWhen All Else Fails...Don’t Go Gipper...Nasa Columbia and Challenger Disasters: When Management Pulls Rank and There Is a Big Disconnect Between the Manager’s View and the Engineer’s ViewBackgroundWhat Can Be LearnedA Look at the OrganizationConclusion of Shuttle InvestigationsSummaryRecommendations
18. Future Build Tools from Microsoft
MSBuildBasic MSBuild DefinitionsVisual Studio Team SystemVisual Studio Team BuildThe Microsoft Shell (MSH, or Monad)SummaryRecommendations
A. Embedded Builds
Nuts and Bolts of the CE Build System
B. Extreme Programming
Extreme Programming FundamentalsTest-Driven Development and RefactoringAn Extreme Programming ScenarioMicrosoft Case StudyReferences and Further Reading
C. Testing Guide
Test Guide: A Compilation from the Developer Division at MicrosoftFile Tests: Does Your Code Rely on Files?File Paths: Are File Paths Ever Given As Input to Your Program?Input from Registry: Is the Registry Used to Store or Retrieve Information?Strings: Do You Input Strings into Your Application?Numeric Values: Does Your Program Take Numeric Values for Input?What Inputs Does Your Web Application Take?Network Connectivity Tests: Are You Connected to a LAN or WAN?General AdviceReferencesTools
D. Debug Symbols
The Windows Scenario That You May Run into with Your Applications
Final Thoughts

Content preview from Build Master, The: Microsoft’s Software Configuration Management Best Practices

Chapter 12. Build Verification Tests and Smoke Tests

	Philosophy: Eating our own dog food.
	--Paul Maritz, former vice president of systems at Microsoft

What does this dog food philosophy mean? As explained in the earlier chapters, we at Microsoft test our own software on our developer, IT, and—in some cases—home systems before we ship a product out the door. In other words, we eat our own dog food. Why is this relevant? The following sidenote illustrates why.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Essential Visual Studio 2019: Boosting Development Productivity with Containers, Git, and Azure Tools

Publisher Resources

ISBN: 0321332059Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Build Master, The: Microsoft’s Software Configuration Management Best Practices

by Vincent Maraia

Chapter 12. Build Verification Tests and Smoke Tests

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.