Confirmed users
753
edits
Auto-tools/Projects/Bisect in the cloud: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/Bisect in the cloud (view source)
Revision as of 12:09, 11 February 2013
, 11 February 2013→Goals & Considerations
| Line 10: | Line 10: | ||
= Goals & Considerations= | = Goals & Considerations= | ||
==Overall Requirements== | |||
* The ability to input a bad and good revision, the test that can reproduce this issue and which tree to run against | |||
* Be able to work again different types of regression like tests or build | |||
* Bisect on Pushes and Revisions | |||
* Output results to be consumed by interfaces like TBPL | |||
* Ability to handle custom test vs running existing test suite | |||
* Have the ability to spawn multiple builds based on group requesting. E.g. Sheriffs have tree closed and need to bisect quickly. | |||
==Considerations== | |||
* Can we extend MozRegression to be core to this so we dont have to do builds again | |||
* Can we use the Self-Serve API for some tasks to make things quicker | |||
* We need be able to reuse RelEng infrastructure to run tasks. | |||
= Non-Goals = | = Non-Goals = | ||