Event information model for Toaster: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
: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> : | :target : <span style="color: red">N/A</span> : #multiple targets possible on a single build; will need to separate machines images | ||
:machine : <span style="color: red">N/A</span> | :machine : <span style="color: red">N/A</span> : #index into all the machines that we support ? | ||
:distro : <span style="color: red">N/A</span> | :distro : <span style="color: red">N/A</span> | ||
:distro_version : <span style="color: red">N/A</span> | :distro_version : <span style="color: red">N/A</span> | ||
| Line 13: | Line 13: | ||
:target_system : <span style="color: red">N/A</span> | :target_system : <span style="color: red">N/A</span> | ||
:layers : : <span style="color: red">N/A</span> # index into the layer table | :layers : : <span style="color: red">N/A</span> # 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 ==== | ==== TASKS ==== | ||
Revision as of 09:27, 13 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 : #multiple targets possible on a single build; will need to separate machines images
- 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
- 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
- dependent_tasks : NOT AVAILABLE
- errors_no : NOT AVAILABLE
- warnings_no : NOT AVAILABLE
- error : NOT AVAILABLE
- warning : NOT AVAILABLE
- sstate_result : NOT AVAILABLE
IMAGES
- uuid # of build that generated the image
- packages # list of packages in that image one to many
- TBC
PACKAGES
- package_id
- recipe # recipe that generated this package
- TBC
FILELIST
- package # id in the list of packages
- complete file path
- file size
- TBC
RECIPES
- name
- layer # point to a layer index
- depends
- TBC
LAYERS
- name
- branch
- commit
- priority
- TBC
VARIABLES
- uuid
- variable_name
- variable_value
