Bug 6671 - The all builds table must also list failed build requests
Summary: The all builds table must also list failed build requests
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium+ normal
Target Milestone: 1.8 M2
Assignee: Alexandru Damian
QA Contact: Mihail Stanciu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-09-02 11:45 UTC by Belen Barros Pena
Modified: 2015-02-17 12:35 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2014-09-02 11:45:50 UTC
With Toaster handling configuration, users need to be able to see builds that fail early because of missing dependencies or because a layer fails to clone. Such builds currently show in the "Recent builds" section of the project page as "failed build requests", but they do not show in the "All builds" page. This is a bit misleading. 

All started builds should show in the "All builds" page, which means that failed build requests should also be listed there.
Comment 1 Alexandru Damian 2014-12-08 12:47:22 UTC
This features brings a change from "interactive mode" - in "managed mode", we need to display "bldcontrol.BuildRequest" items instead of "orm.Build" items.

Technically, this is achieved by implementing the needed design in a "all build requests" page (view buildrequests / template buildrequests.html) and transparently call this view when the builds view is called in managed mode.
Comment 2 Alexandru Damian 2015-01-12 14:59:27 UTC
Posted for review on 

poky-contrib:adamian/20150107-allbuilds-6671
Comment 3 Alexandru Damian 2015-01-20 16:59:34 UTC
Fixed in master.
Comment 4 Mihail Stanciu 2015-02-17 12:35:24 UTC
Verified on master: 6ae933b75c1c34a9d39e1aff0a0cb26a7ce4677f