Each list item represents a (build + image recipe) combination. For example, if I run a build for more than one target (bitbake core-image-minimal core-image-minimal-dev), I will see one list item per target (in the example, one for core-image-minimal and another one for core-image-minimal-dev) For each build + image recipe combination we will see some basic information, such as: * Build status (completed, completed with warnings or failed) * Completion / failure time stamp * Number of warnings thrown by the build (if any) * Number of errors thrown by the build (if any) * Image recipe * Machine * Download option (I can choose one or more images to download, or download them all) etc. The complete information set is TBC. For an idea of this feature, check: http://www.yoctoproject.org/webhob/phase3_final_web_prototype/project.html
When I said 'list item', I meant 'table row'.
Created attachment 1239 [details] Builds table information A first attempt to describe the information that should be available in the builds table.
Created attachment 1244 [details] Builds table information
Created attachment 1245 [details] Builds table information
Created attachment 1248 [details] Builds table information We have concluded that each table row should represent a build, not a build + image recipe combination as previously stated. This means that, for multi-target builds, we'll display all targets within a single table cell.
Created attachment 1250 [details] IA 0.0 All builds
Created attachment 1260 [details] Builds table information
Created attachment 1264 [details] Builds table information
Created attachment 1268 [details] Byi
Created attachment 1269 [details] Builds table information
Created attachment 1297 [details] Builds table information
Created attachment 1302 [details] IA 0.0 All builds
Created attachment 1307 [details] Design 0.0 All builds
Created attachment 1310 [details] IA 0.0 All builds
Created attachment 1311 [details] Design 0.0 All builds
Created attachment 1341 [details] IA 0.0 All builds
Created attachment 1342 [details] Design 0.0 All builds
Created attachment 1390 [details] Design 0.0 All builds
Created attachment 1397 [details] Design 0.0 All builds
Back-end data interface and API implemented. Docs should reflect available API and GUI usage.
Created attachment 1430 [details] Design 0.0 All builds
Created attachment 1468 [details] IA 0.0 All builds
Created attachment 1469 [details] Design 0.0 All builds
Created attachment 1617 [details] Design 0.0 All builds
I believe that all the concerns about the build table are addressed.
verified in master:54562006c1327c5b99daa4cc05a3ba7e38412da1
A case is created in https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=923. Verified in 1f16ca9fba325f5ddbb1edad5bbad78d990de5e0.