You can use Insight to visualize and perform some types of analysis on builds that you executed with BitBake, such as Yocto Project builds. This includes the ability to run certain reports to view BitBake dependency information and aggregate statistics.
You use Accelerator and JobCache for a BitBake build by entering the Accelerator
ebitbake command to run that build. This creates an individual annotation file for each BitBake package and task. To facilitate better analysis with Insight, you use the Accelerator
bb2anno tool to combine these files along with other buildstats data to create a single “pseudo-annotation” file from the build. This tool generates the file from BitBake buildstats data, BitBake build logs and runscripts, and optionally, eMake annotation files for those tasks in the BitBake process that were executed using Accelerator. You load a BitBake pseudo-annotation file into Insight just as you do with any other annotation file.
For details about using the
ebitbake command and the
bb2anno utility, see the KBEA-00171 - Using eMake to Accelerate BitBake Builds Using ElectricAccelerator 11.0.1 KB article for instructions.
Visualizations and Jobs Analysis for BitBake Builds
The following subset of Insight functionality is available for analyzing a pseudo-annotation file generated by eMake:
Main window “timeline” visualization showing tasks executed in the build. For details, see Navigating the Interface.
“Job Details” data for BitBake tasks and any jobs incorporated from eMake annotation files by eMake. For more information, see Job Details Dialog.
Job classification, including “jobs” that represent BitBake tasks not executed using eMake. For details, see the KBEA-00171 - Using eMake to Accelerate BitBake Builds Using ElectricAccelerator 11.0.1 KB article.
Job search, including searches by BitBake task type using
class:class_namesyntax such as
class:patch. For details, see Searching for Jobs.
Using Reports with BitBake Builds
“Why rebuild” data is available only for jobs incorporated from eMake annotation (not for “jobs” created to represented unaccelerated BitBake tasks).
The following reports will not work for BitBake builds:
Other reports and functionality might work partially.