Add worker hardware info to job history in the WebUI

[StefanBruens]

The job history features the build time and the used worker, but this is not sufficient to determine
why one build took significantly longer than a previous one.

This would also help to find failed builds due to unsufficient constraints (e.g. unsufficent memory).

The setup can be retrieved for the last job by reading the build log, i.e. the qemu parameters, but there is no history.

Adding the following information would be appreciated:

• CPU count ("-smp N")
• Physical memory ("-m XXXX")
• Swap size
• Disk size

[adrianschroeter]

On Montag, 17. Juni 2019, 18:41:23 CEST StefanBruens wrote: The job history features the build time and the used worker, but this is not sufficient to determine why one build took significantly longer than a previous one. This would also help to find failed builds due to unsufficient constraints (e.g. unsufficent memory). The setup can be retrieved for the last job by reading the build log, i.e. the qemu parameters, but there is no history. Adding the following information would be appreciated: - CPU count ("-smp N") - Physical memory ("-m XXXX") - Swap size - Disk size

you know that you can request worker hardware already eg via # osc api /worker/x86_64:lamb01:1 ? I don't think it makes sense to copy this data into the history, right?

…

-- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de

[StefanBruens]

I think having these visible in the WebUI would be quite useful:

• no need for the command line
• no need to query info for each worker individually