canmove, Confirmed users
2,850
edits
ReleaseEngineering/BuildFaster: Difference between revisions
ReleaseEngineering/BuildFaster (view source)
Revision as of 21:36, 8 November 2012
, 8 November 2012→Current activities
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) |
||
| Line 44: | Line 44: | ||
| Purchase new machines for win/linux testers that are not tied to aggressive obsolescence schedule | | Purchase new machines for win/linux testers that are not tied to aggressive obsolescence schedule | ||
| coop | | coop | ||
| {{StatusBlocked|status=Underway | | {{StatusBlocked|status=Underway. Various test OSes are being setup and validated.}} | ||
|- | |||
| {{bug|784913}} | |||
| migrate linux xpcshell testsuite to AWS | |||
| jmaher | |||
| {{StatusBlocked|status=Blocked on panda work}} | |||
|- | |- | ||
| {{bug|784913}} | | {{bug|784913}} | ||
| Line 55: | Line 60: | ||
* {{bug|657738}} - Automatically determine when oranges happen and auto-star them (no owner/decision on steps yet) | * {{bug|657738}} - Automatically determine when oranges happen and auto-star them (no owner/decision on steps yet) | ||
* Windows builds on AWS are still too slow, but we can revisit this regularly | * Windows builds on AWS are still too slow, but we can revisit this regularly | ||
* | * Cross-compile Mac builds on AWS | ||
** after legal review, *yes* we think we can do this. Need to find a developer owner to give this a try. | |||
* {{bug|772579}} - Can we run unittests on AWS for Linux (and eventually Windows)? | * {{bug|772579}} - Can we run unittests on AWS for Linux (and eventually Windows)? | ||
* Analyze methods of understanding and optimizing what we run on a per-checkin basis | * Analyze methods of understanding and optimizing what we run on a per-checkin basis | ||
** Test code related to the current patch? | ** Test code related to the current patch? | ||
** Run full tests only every x pushes or y time (whichever occurs first). Between those only run a set of tests related to the patch at hand. (Would need developer override and on-demand testing ability) | ** Run full tests only every x pushes or y time (whichever occurs first). Between those only run a set of tests related to the patch at hand. (Would need developer override and on-demand testing ability) | ||
* less frequent debug builds | * less frequent debug builds | ||
* use an optimized xpcshell + httpd.js to run debug tests (depends on {{bug|669953}}) | * use an optimized xpcshell + httpd.js to run debug tests (depends on <s>{{bug|669953}}</s>) | ||
= Data we need = | = Data we need = | ||