Bug 5015 - api: create final definition of webhob APIs
Summary: api: create final definition of webhob APIs
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: High enhancement
Target Milestone: 1.5 M4
Assignee: Alexandru Damian
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 4948 5016
  Show dependency tree
 
Reported: 2013-08-14 14:28 UTC by Alexandru Damian
Modified: 2013-10-03 13:13 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
API review (11.85 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-08-19 11:08 UTC, Belen Barros Pena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Damian 2013-08-14 14:28:29 UTC
Create and document the definition of webhob REST API targeted for 1.5 as to supply all information needed for frontend elements.
Comment 1 Alexandru Damian 2013-08-14 17:01:19 UTC
The REST API contracts are documented here.

https://wiki.yoctoproject.org/wiki/REST_API_Contracts

As of 15th August, this document supercedes all other REST API documents.
Comment 2 Alexandru Damian 2013-08-15 13:41:40 UTC
The APIs for object retrieval have been defined.

Please review the link above and let me know if there is something missing.

The dependency data for Tasks, Recipes and Packages have to be defined.
Comment 3 Alexandru Damian 2013-08-15 14:31:29 UTC
Final version of the REST API done.

Please review and re-open this bug with specific comments regarding any missing info that would be needed in the frontend.
Comment 4 Belen Barros Pena 2013-08-19 11:08:20 UTC
Created attachment 1432 [details]
API review
Comment 5 Belen Barros Pena 2013-08-19 11:09:09 UTC
Alex and Belen went through the API (see attached spreadsheet) and found that the following needs to be added:

* output full file name (the full name of the files that constitute the outcome of the build)

* full path to task script

* task covered by (if possible)

* errors content (we are already collecting this but we need an API call for it)

* warnings content (we are already collecting this but we need an API call for it)

* diffsigs command output

* is package included in rootfs?

* package files (location in disk of package files)

* package license

* package depends / recommends / brought in by

* names of files generated by each package

* size of files generated by each package
Comment 6 Alexandru Damian 2013-09-09 12:12:09 UTC
The APIs updated https://wiki.yoctoproject.org/wiki/REST_API_Contracts

Known missing features:
> 
> * diffsigs command output

* needs extensive re-working of the bitbake server protocol since we need to execute commands back on a remote server, which is not supported in Stage 1. 
Propose deferring.
Comment 7 Belen Barros Pena 2013-09-11 15:13:31 UTC
Apart from the(In reply to comment #6)
> The APIs updated https://wiki.yoctoproject.org/wiki/REST_API_Contracts
> 
> Known missing features:
> > 
> > * diffsigs command output
> 
> * needs extensive re-working of the bitbake server protocol since we need to
> execute commands back on a remote server, which is not supported in Stage 1. 
> Propose deferring.

Apart from the diffsigs command output (moved to 1.6), I am also missing the 'covered by' information for tasks, although AlexD has mentioned this can be obtained with a database query on the information we are already collecting.
Comment 8 Andreea Brandusa Proca 2013-10-03 13:13:34 UTC
Verified.