Event information model for Toaster: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
(Add builds information)
Line 7: Line 7:
:uuid : <span style="color: green">DONE</span> : unique task id
:uuid : <span style="color: green">DONE</span> : unique task id
:target : <span style="color: red">N/A</span> : # OneToMany to the targets table
:target : <span style="color: red">N/A</span> : # OneToMany to the targets table
:machine : <span style="color: green">DONE</span> : # index into all the machines that we support ? # we can ask bitbake for the machine variable
:machine : <span style="color: green">DONE</span> : # index into all the machines that we support ? # we can ask bitbake for the MACHINE variable
:distro : <span style="color: green">DONE</span> : # we can ask bitbake for the distro variable
:distro : <span style="color: green">DONE</span> : # variable - DISTRO
:distro_version : <span style="color: green">DONE</span> : # we can ask bitbake for the distro version variable
:distro_version : <span style="color: green">DONE</span> : # variable - DISTRO_VERSION
:host_system : <span style="color: red">N/A</span>
:host_system : <span style="color: green">DONE</span> : # variable - BUILD_SYS
:host_distribution : <span style="color: red">N/A</span>
:host_distribution : <span style="color: green">DONE</span> # variable - NATIVELSBSTRING
:target_system : <span style="color: red">N/A</span>
:target_system : <span style="color: green">DONE</span> # variable - TARGET_SYS
:layers :  :  <span style="color: green">DONE</span> # index into the layer table ? # we can ask bitbake for the list (BBLAYERS)
:layers :  :  <span style="color: green">DONE</span> # index into the layer table ? # we can ask bitbake for the list (BBLAYERS)
:started_on : <span style="color: red">N/A</span> # Is there a build started event we can use ?
:started_on : <span style="color: green">DONE</span> # use BuildStarted event
:completed_on <span style="color: red">N/A</span> # Is there a build success event or should we grab this when events processing has ended ?
:completed_on <span style="color: green">DONE</span> # use BuildCompleted event
:outcome : <span style="color: green">DONE</span> # We can grab this at the end of all commands by checking the errors number or the return value.
:outcome : <span style="color: green">DONE</span> # We can grab this at the end of all commands by checking the errors number or the return value.
:number_of_errors <span style="color: red">N/A</span>  
:number_of_errors <span style="color: green">DONE</span> # total number of log events with level of ERROR (see knotty)
:number_of_warnings <span style="color: red">N/A</span>  
:number_of_warnings <span style="color: green">DONE</span> # total number of log events with level of WARNING (see knotty)
:cpu_usage : <span style="color: red">N/A</span>  # it's in the build stats; we don't have a meaning
:cpu_usage : <span style="color: red">N/A</span>  # it's in the build stats; we don't have a meaning
:disk_io : <span style="color: red">N/A</span>  # it's in the build stats; we don't have a meaning
:disk_io : <span style="color: red">N/A</span>  # it's in the build stats; we don't have a meaning
:log : <span style="color: red">N/A</span>  # main cooker log
:log : <span style="color: red">DONE</span>  # main cooker log - composed of all log events over the set log level (see knotty)
:output : <span style="color: red">N/A</span>  # list of generated files; downloads
:output : <span style="color: red">N/A</span>  # list of generated files; downloads - please check how Hob does this
:build_name : <span style="color: red">N/A</span>  # bitbake generates a name
:build_name : <span style="color: green">DONE</span>  # variable - BUILDNAME
:bitbake_version : <span style="color: red">N/A</span>  
:bitbake_version : <span style="color: green">DONE</span> # variable - BB_VERSION





Revision as of 12:34, 19 June 2013


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 : DONE : # index into all the machines that we support ? # we can ask bitbake for the MACHINE variable
distro : DONE : # variable - DISTRO
distro_version : DONE : # variable - DISTRO_VERSION
host_system : DONE : # variable - BUILD_SYS
host_distribution : DONE # variable - NATIVELSBSTRING
target_system : DONE # variable - TARGET_SYS
layers :  : DONE # index into the layer table ? # we can ask bitbake for the list (BBLAYERS)
started_on : DONE # use BuildStarted event
completed_on DONE # use BuildCompleted event
outcome : DONE # We can grab this at the end of all commands by checking the errors number or the return value.
number_of_errors DONE # total number of log events with level of ERROR (see knotty)
number_of_warnings DONE # total number of log events with level of WARNING (see knotty)
cpu_usage : N/A # it's in the build stats; we don't have a meaning
disk_io : N/A # it's in the build stats; we don't have a meaning
log : DONE # main cooker log - composed of all log events over the set log level (see knotty)
output : N/A # list of generated files; downloads - please check how Hob does this
build_name : DONE # variable - BUILDNAME
bitbake_version : DONE # variable - BB_VERSION


TASKS

uuid : DONE -> generated at the beginning of each build.
task_id :N/A
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 : N/A
path_to_sstate_obj : N/A
recipe : DONE -> retrieved from event._package
task_name : DONE -> retrieved from event._task
  • index on recipe / task_name
source_url : N/A
log_file: N/A
work_directory : N/A
script_type : N/A
file_path : N/A
line_number : N/A
py_stack_trace : N/A
disk_io : N/A
cpu_usage : N/A
elapsed_time : DONE -> difference between started and finished time
errors_no : N/A
warnings_no : N/A
error : N/A
warning : N/A
sstate_result : N/A
diffsigs : N/A

TASK DEPENDENCY

task_id : N/A
depends_on : N/A # still a task_id

TARGETS

uuid : N/A # of build that generated the image
is_image : N/A
  1. TBC

ARTIFACTS

uuid : N/A
target_id : N/A
file_name : N/A
file_size : N/A

PACKAGES IN IMAGES

package_id : N/A
target_id : N/A

PACKAGES

package_id : N/A
recipe : N/A # recipe that generated this package
name : N/A
version : N/A
size : N/A

PACKAGE DEPENDENCIES

package_id : N/A
depends_on : N/A

FILELIST

package_id : N/A # id in the list of packages
complete file path : N/A
file size : N/A

RECIPES

name : N/A
version : N/A
layer : N/A # point to a layer index
summary : N/A
description : N/A
section : N/A  ?
license : N/A
licensing info: N/A ?
homepage : N/A  ?
bugtracker : N/A  ?
author : N/A  ?
file_path : N/A  ?

RECIPE DEPENDENCY

recipe_id : N/A
depends_on : N/A # also a recipe id

LAYERS

name : N/A
branch : N/A
commit : N/A
priority : N/A
link to oecore layer index: N/A  ?
  1. TBC

VARIABLES

uuid : N/A
variable_name : N/A # a list of `bitbake -e`
variable_value : N/A
file : N/A # a single file name where the variable is set
changed : N/A
human_readable_name : N/A
description : N/A

MACHINES

name : N/A
description : N/A