Toaster: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
Line 3: Line 3:
General discussion about '''Web Hob''' happens on a dedicated mailing list: [https://lists.yoctoproject.org/listinfo/webhob https://lists.yoctoproject.org/listinfo/webhob]
General discussion about '''Web Hob''' happens on a dedicated mailing list: [https://lists.yoctoproject.org/listinfo/webhob https://lists.yoctoproject.org/listinfo/webhob]


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


== User interface ==
== User interface ==
The design of the user interface takes place in iterations, and most recent designs supersede older ones.  
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.
Here is a set of links to design documentation.
Line 20: Line 19:
* [[WebHob_Design]]
* [[WebHob_Design]]
* [[Yocto Web Hob Design 0.0 — Archived|A preliminary design project]] by [http://www.jimkosem.com/ Jim Kosem]
* [[Yocto Web Hob Design 0.0 — Archived|A preliminary design project]] by [http://www.jimkosem.com/ Jim Kosem]
== 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.
[[https://bugzilla.yoctoproject.org/buglist.cgi?list_id=38454&bug_severity=enhancement&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&component=web-hob&target_milestone=1.5&target_milestone=1.5%20M1&target_milestone=1.5%20M2&target_milestone=1.5%20M3&target_milestone=1.5%20M4&target_milestone=1.5%20M5&product=Web%20-%20Hob WebHob Bugzilla feature list]]


== Architecture and component design ==
== Architecture and component design ==
Line 26: Line 36:


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.
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.


* [[ WebHob general architecture ]]
* [[ WebHob general architecture ]]
Line 38: Line 46:


== Testing ==
== Testing ==
Documentation and results related to WebHob Quality Assurance.
* [[WebHob testing plan ]]
* [[WebHob testing plan ]]


 
=== QA Reports and Bugzilla entries ===
 


== Old page content ==
== Old page content ==

Revision as of 17:06, 23 May 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

We provide a manual for installation and running WebHob as part of this wiki.

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.