Support:Sumodev/Continuous Deployment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
{{draft}} | |||
By the end of 2011, [[Support:Sumodev|Support Engineering]] wants to move from big releases to '''Continuous Deployment'''. There's lots to do to reach that goal. | By the end of 2011, [[Support:Sumodev|Support Engineering]] wants to move from big releases to '''Continuous Deployment'''. There's lots to do to reach that goal. | ||
Revision as of 20:58, 3 January 2011
|
THIS PAGE IS A WORKING DRAFT | 
|
| The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page. |
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
There is a qualitative difference between deciding which work to group into a release and when to fix small bugs when changes go live immediately. Our concept of planning will have to change.
- Push every week. (By end of Q2.)
- Push every day.
- Push several times per day.
Features
- Support feature flags.
- Support features per group or percentage.