There are several options and levels for removing builds from Toaster interface. (a) Hide builds from a project This option simply removes or hides selected builds from the Toaster display, for example builds quickly halted because the owner realized that they missed a setting. The database records and the project on the disk is untouched. This un-clutters the display, yet requires little programing (and development time). This implies that there would be a page that can show all builds, and allow users to unhide selected builds. (b) Delete builds from a project This option is where a selected build and all its related database records are removed from the database. This removes the database overhead for this unwanted builds. The project on the disk is untouched. Since the database should be normalized, this operation should be clean and not interfere with other builds.
Assigning this first to Belén for the design phase.
So, best case scenario is I have time to design something and the dev team has time to implement it. Worst case scenario we extend the builddelete command to delete projects as well.
The delete functionality is dependent on the user authentication and permission enforcement to prevent data loss through unauthorized delete operations.
setting to 'future' until we discuss new features for upcoming releases
we should probably tackle all delete features within 2.2: see also bug 8132 and bug 9184
Created attachment 3298 [details] Design - Deleting builds and projects
The build dashboard page currently has buttons for "Download build log" "New custom image", should the delete also be a button or a link as is on http://www.yoctoproject.org/toaster/b3/build-dashboard.html ?
(In reply to comment #7) > The build dashboard page currently has buttons for "Download build log" "New > custom image", should the delete also be a button or a link as is on > http://www.yoctoproject.org/toaster/b3/build-dashboard.html ? All the options in the "Actions" section of the left navigation should be turned into links. I tried to explain on page 3 of the design document: https://bugzilla.yoctoproject.org/attachment.cgi?id=3298 Any other questions, let me know.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0d70606022cad010f586ec29b558ee902be765ef