Bug 10466

Summary: Update BuildLog with build progress
Product: [Infrastructure] AutoBuilder Reporter: Joshua Lock <joshuagloe>
Component: autobuilderAssignee: Joshua Lock <joshuagloe>
Status: RESOLVED FIXED QA Contact: Juan Ramos <juan.fernandox.ramos.frayle>
Severity: enhancement    
Priority: Medium+ CC: infras.ab.watcher, Infras.watcher, jose.perez.carranza, pidge, randy.macleod
Version: 2.2   
Target Milestone: 2.3 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 10502    

Description Joshua Lock 2016-10-20 13:18:01 UTC
The BuildLog page on the wiki would be much more useful if it were also updated with build results.

Any failures could be added to the wiki with a link to the relevant logs. If a build succeeds the BuildLog entry could be updated to note no issues were found.
Comment 1 Joshua Lock 2016-11-09 13:49:08 UTC
We can use the same JSON api to monitor the build, i.e. (a transient url):
https://autobuilder.yoctoproject.org/main/json/builders/nightly/builds/1059?as_text=1

Triggered builds are currently the 25th buildstep (index 24 in the steps array of the JSON data) and contains a urls dictionary of build → url mappings.

We can use the urls to determine an api to monitor for failures and check the steps of each monitored build for a failure code (after determining what possible values there are) in the results array and/or the string "failed" in the text array.
Comment 2 Joshua Lock 2016-11-17 14:23:56 UTC
I have an initial set of changes for the buildlogger script to implement this, I'm not very happy with some pieces of the code and would like to fix them up over the next day or so.

There's also an issue in that since we renamed meta-yocto to meta-poky during krogoth the GetLayerVersion_3 build step always fails, which results in a false positive when reporting failures through buildlogger.

It's probable that we can just drop this step now, so long as the autobuilder doesn't need to support jethro or earlier any more.
Comment 3 Joshua Lock 2016-11-30 13:34:35 UTC
The code is implemented but taking some time to test due to the length of time it takes to run through a build on the autobuilder.