670
edits
Continuous Integration: Difference between revisions
Jump to navigation
Jump to search
→Program Description: Added requirements
(→Program Description: Entered program description) |
(→Program Description: Added requirements) |
||
| Line 3: | Line 3: | ||
=='''Program Description'''== | =='''Program Description'''== | ||
The purpose of the Firefox OS Quality initiative is to drive the engineering team to Continuous Integration through testing platform improvements, test improvements, test automation and code coverage, where every commit on Gecko and Gaia triggers a full test run, with failures and performance issues reported on Treeherder for immediate backout. | The purpose of the Firefox OS Quality initiative is to drive the engineering team to Continuous Integration through testing platform improvements, test improvements, test automation and code coverage, where every commit on Gecko and Gaia triggers a full test run, with failures and performance issues reported on Treeherder for immediate backout. | ||
===Requirements:=== | |||
The following Firefox OS 2.6 work must be completed to achieve Continuous Integration: | The following Firefox OS 2.6 work must be completed to achieve Continuous Integration: | ||
| Line 27: | Line 29: | ||
* Achieve ability for sheriffs to back out commits if post-commit data is bad | * Achieve ability for sheriffs to back out commits if post-commit data is bad | ||
* Ability to block commits with pre-commit testing | * Ability to block commits with pre-commit testing | ||
===User Stories and Acceptance Criteria=== | ===User Stories and Acceptance Criteria=== | ||