Automated Build

  • Summary: This standard defines an automated build process
  • Details:

  • Status: MANDATORY STANDARD, approved June 01, 2006

  • Scope: All teams should use this process when publishing or deploying software

  • Rationale: We don't have enough engineers to staff a third shift.

  • Objectives and Requirements:
    • Create an automated build process.
    • Process should run without human oversight.
    • Process needs to start and end within an 8 hour period

  • FAQ:
    • Q: Why do we need an automated build process A: An automated process allows us to run builds over night without engineers needing to be on site.

  • ESG Contact: Bob S

  • Engineering Contact: Build & Release Team (build-team@company)
Topic revision: r1 - 29 Mar 2014, VickiBrown
This site is powered by Foswiki Copyright © by the contributing authors. All material on this wiki is the property of the contributing authors.
Foswiki version v2.1.6, Release Foswiki-2.1.6, Plugin API version 2.4
Ideas, requests, problems regarding CFCL Wiki? Send us email