ReleaseEngineering/BuildFaster: Difference between revisions
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) (→People) |
ChrisCooper (talk | contribs) |
||
| Line 10: | Line 10: | ||
** Improve set-up time | ** Improve set-up time | ||
* Gather data for devs to tackle test jobs that take long | * Gather data for devs to tackle test jobs that take long | ||
* Speeding up the build system itself: | |||
** (universal-singlepass) less painful universal builds on mac (build universal as a single pass) - {{bug|417044}} | |||
** makefiles: split of config/rules.mk into a hierarchy of makefiles - {{bug|662833}} | |||
= People = | = People = | ||
Revision as of 20:59, 13 June 2011
Goals
- Get time from build-available to all tests done to <= 30 minutes
- Get per-checkin build time to under 2 hours for all platforms
Current activities
- Set up metrics to quantify our current end-to-end time, and be able to track it
- Do non-PGO opt builds for linux and windows bug 658313
- Investigate if we can do 64-bit only 10.6 builds per-checkin. Need to determine if there are many 10.5 only test failures.
- Determine which suites to be merged with others - bug 659328
- Improve set-up time
- Gather data for devs to tackle test jobs that take long
- Speeding up the build system itself:
- (universal-singlepass) less painful universal builds on mac (build universal as a single pass) - bug 417044
- makefiles: split of config/rules.mk into a hierarchy of makefiles - bug 662833
People
- Chris AtLee (:catlee)
- Armen Zambrano (:armenzg)
- Joey Armstrong (:joey)
Definitions
- end-to-end time
- The time between a change being pushed to HG and all builds and test results being available
- per-checkin build
- Opt and debug builds that are triggered by a new checkin