| Summary: | Show git clone progress in most recent builds area | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Elliot Smith <elliot.smith> |
| Component: | toaster | Assignee: | David Reyna <david.reyna> |
| Status: | RESOLVED FIXED | QA Contact: | Libertad <libertad.gonzalez.de.la.cruz> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | belen.barros.pena, brian.avery, david.reyna, jessica.zhang, stanciux.mihail |
| Version: | 2.3 | ||
| Target Milestone: | 2.4 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 9631 | ||
| Bug Blocks: | |||
|
Description
Elliot Smith
2016-07-12 16:13:24 UTC
Want to keep as one story, but break up commits into front end and backend. We actually do have the build object while the cloning is performed. If we did not there would be any progress bar at all, since in the current implementation all progress information is shared with the GUI via the build record. FYI, this is actually a long term problem in that Toaster is inappropriately using the database as an RPC, and every incremental progress update for parsing and tasks causes a record update. This results in massive database transactions for purely transient data. Brian had looked at a long term solution using perhaps Rabbit (message queues) and Celery (multi-threading python support). |