Event information model for Toaster

This is the information we need for completing the tables of the WebHOB database.

BUILDS

uuid : DONE : unique task id

target : N/A : # OneToMany to the targets table

machine : N/A : # index into all the machines that we support ?

distro : N/A

distro_version : N/A

host_system : N/A

host_distribution : N/A

target_system : N/A

layers :  : N/A # index into the layer table

started_on

completed_on

number_of_errors

number_of_warnings

cpu_usage : # it's in the build stats; we don't have a meaning

disk_io : # it's in the build stats; we don't have a meaning

log : # main cooker log

output : # list of generated files; downloads

build_name : # bitbake generates a name

TASKS

uuid : DONE -> generated at the beginning of each build.

task_id : NOT AVAILABLE

order : DONE -> counted on each TaskStarted event

task_executed : DONE -> set to True for each TaskStarted event

outcome : DONE? -> retrieved from event.getDisplayName() # is this OK ?

sstate_checksum : NOT AVAILABLE

path_to_sstate_obj : NOT AVAILABLE

recipe : DONE -> retrieved from event._package

task_name : DONE -> retrieved from event._task

• index on recipe / task_name

source_url : NOT AVAILABLE

log_file: NOT AVAILABLE

work_directory : NOT AVAILABLE

script_type : NOT AVAILABLE

file_path : NOT AVAILABLE

line_number : NOT AVAILABLE

py_stack_trace : NOT AVAILABLE

disk_io : NOT AVAILABLE

cpu_usage : NOT AVAILABLE

elapsed_time : DONE -> difference between started and finished time

errors_no : NOT AVAILABLE

warnings_no : NOT AVAILABLE

error : NOT AVAILABLE

warning : NOT AVAILABLE

sstate_result : NOT AVAILABLE

TASK DEPENDENCY

task_id

depends_on # still a task_id

TARGETS

uuid # of build that generated the image

is_image

packages # list of packages in that image one to many

1. TBC

PACKAGES

package_id

recipe # recipe that generated this package

name

version ?

size

PACKAGE DEPENDENCIES

package_id

depends_on

FILELIST

package # id in the list of packages

complete file path

file size

1. TBC

RECIPES

name

version

layer # point to a layer index

summary

description

section ?

license

licensing info ?

homepage ?

bugtracker ?

author ?

file_path ?

RECIPE DEPENDENCY

recipe_id

depends_on # also a recipe id

LAYERS

name

branch

commit

priority

link to oecore layer index ?

1. TBC

VARIABLES

uuid

variable_name # a list of `bitbake -e`

variable_value

file : # a single file name where the variable is set

human_readable_name

description

MACHINES

name

description