Support:Sumodev/Continuous Deployment

From MozillaWiki
< Support:Sumodev
Revision as of 22:54, 27 December 2010 by Jsocol (talk | contribs) (Created page with "By the end of 2011, Support Engineering wants to move from big releases to '''Continuous Deployment'''. There's lots to do to reach that goal. == Measurable ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

By the end of 2011, Support Engineering wants to move from big releases to Continuous Deployment. There's lots to do to reach that goal.

Measurable Goals

  • A bugfix reaches production within 30 minutes of being checked in.

Action Items

Testing

  • Expand unit test suite to cover front end and JavaScript.
  • Organize test suite into unit/functional/acceptance/etc.
  • Work with Web QA Automation to maximize automated coverage and combine results.
  • Automated performance tests.
    • Aggregation and graphs.

Infrastructure

  • Define a secure, defensive, robust flow from source control to production.
    • If someone steals James' laptop, breaks in, and commits an infinite loop, that change should not reach production.
  • Automate push process.

Release Planning

  1. Push every week. (By end of Q2.)
  2. Push every day.
  3. Push several times per day.

Features

  • Support feature flags.
  • Support features per group or percentage.