Implementation - Process

• Perform compiles/links
  • Assign build drive (provides for toggling between OMAKE and NMAKE builds)
  • Execute shared library build script
  • Execute subsystem build scripts distributed across multiple PCs
  • Store labeling log to standard shared network location
  • Perform database build and store log
• Check for errors
  • Use audit to scan build logs for errors, warnings, and activity summary
  • Use script to take view inventory (check for missing build products)
  • Notify developers of any errors or non-approved warnings
• Distribute deliverable build products to standard shared network location under directory with embedded build id. Example: \SCM\builds\S_PS101.0-713
• Install on SCM PC and perform standard Quick Test
• If Quick Test passes, send general notice of build availability
• Generate reports to standard shared network location
  • Source file lists by VOB
  • Configuration records (provides impact cross reference)
  • History matrix
  • Summary build log

Previous slide

Next slide

Back to first slide

View graphic version