Toaster: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
m (→‎Installation and Running: correct poky-contrib link)
Line 51: Line 51:
* prerequisites: TCP ports 8000 for web interface, and 8200 for the bitbake xmlrpc interface
* prerequisites: TCP ports 8000 for web interface, and 8200 for the bitbake xmlrpc interface


* checkout the poky tree. currently [[ http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=webhob-poky/master ]]
* checkout the poky tree. currently http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=webhob-poky/master
* set up a build as normal: <code>  source poky/oe-init-build-env </code>
* set up a build as normal: <code>  source poky/oe-init-build-env </code>
* at this point edit local.conf, or layers, etc.
* at this point edit local.conf, or layers, etc.

Revision as of 15:10, 9 July 2013

WebHob is a Web-based interface to the Bitbake build system and the Poky distribution inside the Yocto Project.

General discussion about Web Hob happens on a dedicated mailing list: https://lists.yoctoproject.org/listinfo/webhob

Project planning is available below, are the design documents we follow.

User interface

The design of the user interface takes place in iterations, and most recent designs supersede older ones. Here is a set of links to design documentation.

WebHob clickable prototype

Old design documents

Project Planning

We plan to develop WebHob functionality in stages. Each stage should match with an Yocto Project release.

YP 1.5 release

  • WebHob will offer features to record and analyze bitbake runs, where a bitbake run is an invocation of bitbake to a certain target.
  • WebHob will offer ways to inspect the system image contents generated by running a Poky target that results in a disk image.

[WebHob Bugzilla feature list]

Architecture and component design

We are planning the capabilities of WebHob based on evolutive stages of implementation, using community feedback on each stage to plan, design and implement a set of capabilities for the next stage. In the first stage, synchronized with the planning of Yocto 1.5, we'll implement a build analysis / image inspection module.

WebHob is designed as a collection of components that will run independently performing isolated functions. The interfaces between components are documented on this wiki as to ease interoperability with newer components. From design phase, we've taken care to account for further expansion needs, and account for scalability problems.

Installation and Running

To get it up and running:

  • prerequisites: TCP ports 8000 for web interface, and 8200 for the bitbake xmlrpc interface

A bunch of files are created and used under the build/ directory:

  • webhob.sqlite - the database file
  • whbmain.log - the log file of the web server
  • whbmain.pid - contains the pid of the web server
  • dsi.pid - contains the pid of the DSI data bridge
  • bitbake-cookerdaemon.log - the log file of the bitbake server


For more details, including how it runs, see A manual for installation and running WebHob .

Testing

Documentation and results related to WebHob Quality Assurance.

QA Reports and Bugzilla entries

Old page content

This page is about the Web Hob project. Web Hob is a web-based interface to the Yocto Project.

General discussion about Web Hob happens on a dedicated mailing list: https://lists.yoctoproject.org/listinfo/webhob

There have been 2 main pieces of work related to Web Hob so far:

Web Hob information architecture

This document represents the content structure of the Web Hob application.

File:Web Hob content structure.pdf

Different approaches to multi-user workflows

This document outlines the different approaches we have uncovered so far to facilitate multi-user and team work with Web Hob.

Visualisations index

The build analysis functionality in Web Hob will include several graphical presentations of build data. The first step to design them is listing them all.