Hi Ionut, Some comments inline from the UI standpoint.
Cheers Belén On 25/11/2014 09:48, "Chisanovici, IonutX" <[email protected]> wrote: >Hi all, > >I have some questions and thoughts that I want to share with you guys >before starting adding new toaster backend tests. >Below is what I discovered and what my feelings are related to what a >user can do with the new toaster implementations: > >1. From "All builds" there is no link that allow users to see the >projects already started. With this "issue", user is not able to trigger >a new build under an already started project. The only way to see the >already started projects is > to click on one already done build to enter to its project. There is a >need to have a button, link in the ŒAll builds¹ page which will allow >user to jump directly to the opened projects or to one particular project. I am not sure what you are looking at, but the all builds page does have a toggle button that allows you to switch between a table of builds and a table of projects. This should be available in master:67261e2d7a2acd2646b4e25ab1456bec07e93834 It is still work in progress (design spec is not fully implemented yet), but by selecting 'all projects' in this toggle button you should see a table with all your existing projects. >2. Toaster "New project" button/page, allows users to create a new >project having the same name. In the database, toaster will create as >much projects having the same name as user adds. Informations of a new >project with the same name its > being duplicated in the DB in all tables. You are right: at the moment, nothing is stopping you from creating 2 projects with the same name. You might want to open a feature in Bugzilla to stop this from happening. You can assign it to me for the time being, since it will require some design. >3. "New build" button functionality doesn't work, despite a project is >started. The new build button is working on master:67261e2d7a2acd2646b4e25ab1456bec07e93834 >4. Error messages from table "bldcontrol_brerror" should be the same as >the ones from table "orm_logmessage" ? >5. Only the last targets of the projects are appearing in the >"orm_projecttarget". Is that ok ? If yes, what's the point ? >6. Duplicate layers in table "orm_layer". The 'meta-yocto' and >'meta-yocto-bsp' layers appears twice in this table (one from yocto/poky >git and one from openembedded layer index). Is this ok ? Those layers exist in 2 places: the poky repository and the openembedded repository. Toaster allows you to use such core layers either from the poky repo or the openembedded repo, but prevents you from mixing core layers from both. This is done using releases as configured in the toasterconf.json file. AlexD can give you more details about this. > >My personal opinion: I think we save a lot of unneeded/duplicate and >sometime ambiguous informations in the database tables. >I did 2 projects with 3-4 build for each and I saw a lot of duplicated >informations in the tables and especially in these tables: >bldcontrol_brlayer, bldcontrol_brbitbake (all records in this tables are >practically the same), orm_projectlayer > (ambiguous information), orm_projecttarget (??? why this is need it ?), >orm_projectvariable (in my opinion there are no project variables but >build variables, once again ambiguous informations). > >Cheers, >Ionut C > -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
