| Summary: | Cache data to improve UI accuracy | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | hob | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | VERIFIED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | jessica.zhang, jiajun.xu, lianhao.lu, liping.ke, poky.bs.watcher, poky.watcher, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
| Bug Depends on: | 1565 | ||
| Bug Blocks: | |||
|
Description
Joshua Lock - Disabled
2011-08-02 15:08:58 UTC
Things we would like to be able to do but which rely on data generated during a build: * predict the size of the resultant image * more accurately reflect image contents, per bug 1263 Collect data at build time to allow hob to: predict the size of the generated image, more accurately reflect the built image contents, etc. This will likely involve generating data on the autobuilder which the UI can fetch and consume (with local caching for offline usage). This could make use of the existing buildstats data collection and/or may also hook into the package history code where it could also obtain package size information. We'll likely build hob UI around the general infrastructure developed in bug 1565 no longer applicable, see the last comments Hobv2 achieves this another way |