Bug 9023

Summary:

Improve the content of the "other artifacts" section

Product:

[Build System, Metadata & Runtime] Toaster

Reporter:

Belen Barros Pena <belen.barros.pena>

Component:

toaster

Assignee:

Elliot Smith <elliot.smith>

Status:

RESOLVED FIXED

QA Contact:

Libertad <libertad.gonzalez.de.la.cruz>

Severity:

enhancement

Priority:

Medium+

CC:

belen.barros.pena, bluelightning, jessica.zhang, stanciux.mihail

Version:

2.0

Target Milestone:

2.2 M2

Hardware:

x86

OS:

Multiple

Whiteboard:

GUI design available

OS type for building Yocto:

---

Type of Regression:

---

Verified:

Documentation change:

No (bug/feature does not impact docs)

Attachments:

Description	Flags
Design - Displaying the package manifest	none
Design - Displaying build artifacts	none

Description Belen Barros Pena 2016-02-01 17:42:15 UTC

To determine the content for the 'other artifacts' section in Toaster, we currently do the following: we look in the images directory, and for any file we find which isn't already associated with a build, we associate it with the most recent build. 

This means that if I build core-image-minimal for intel-corei7-64, and then I build core-image-base for intel-corei7-64, the first build (core-image-minimal) will show as other artifacts

README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt

bzImage--4.1.15+git0+46bb64d605_788dfc9859-r0-intel-corei7-64-20160128121022.bin 

microcode_20151106.cpio 

modules--4.1.15+git0+46bb64d605_788dfc9859-r0-intel-corei7-64-20160128121022.tgz 

The second build (core-image-base) will show as other artifacts:

core-image-minimal-intel-corei7-64-20160201170430.rootfs.manifest 

This doesn't quite make sense, and could be improved upon:

1. We should exclude the 'README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt' file from all Toaster builds.

2. The 'other artifacts' section should show the list of all files in the images directory that are not rootfs files.

3. The rootfs.manifest files should be associated with the build that created them, and displayed outside of the 'other artifacts' list to avoid issues with the logic in number 2. See the attached design document.

Comment 1 Belen Barros Pena 2016-02-01 17:46:53 UTC

Created attachment 2957 [details]
Design - Displaying the package manifest

Comment 2 Belen Barros Pena 2016-02-04 11:23:50 UTC

I don't think this should be set to 'future'. Build artifacts are the most important thing from a user's perspective: they are the reason why you run builds in the first place! I think it's worth doing the best we can when it comes to presenting them. 

I've changed the milestone to 2.2. I hope that's ok.

Comment 3 Belen Barros Pena 2016-05-06 08:40:32 UTC

*** Bug 9600 has been marked as a duplicate of this bug. ***

Comment 4 Belen Barros Pena 2016-06-13 16:23:50 UTC

Created attachment 3235 [details]
Design - Displaying build artifacts

It looks we may be able to remove the "Other artifacts" section, associating all artifacts to build targets instead. Design document updated accordingly.