releng-scripts use build-info values for LAVA metadata
Description
The AGL builds now produce a `build-info` file containing a handful of bitbake environment variables.
Examine these values and decide which ones can be useful for releng-scripts to use to generate more useful metatdata for LAVA jobs.
For example, today we're using dummy values like `AGL-yocto` and `agl-commit`. These should be replaced with meaningful values.
Environment
None
Attachments
1
100% Done
Activity
Show:
Kevin Hilman
March 22, 2019 at 4:21 PM
Upload of build-info now working
Kevin Hilman
March 21, 2019 at 10:32 PM
So, with the upload for CI jobs done, and the upload for release/snapshot jobs already done automatically, this patch should handle the fetch and cat/source for both CI and release/snapshot jobs: https://gerrit.automotivelinux.org/gerrit/#/c/20770/
Kevin Hilman
March 21, 2019 at 10:16 PM
And for release jobs, the whole tmp/deploy dir is rsync'd, so it should be part of the uploads already.
OK, turns out this is a bit more complicated. The build-info file is generated by the build jobs (CIB), but not saved/uploaded anwhere, so it's not going to be available for the CIBT jobs. So before we can use it in a CIBT job, we have to modify the CIB jobs to upload it.
The AGL builds now produce a `build-info` file containing a handful of bitbake environment variables.
Examine these values and decide which ones can be useful for releng-scripts to use to generate more useful metatdata for LAVA jobs.
For example, today we're using dummy values like `AGL-yocto` and `agl-commit`. These should be replaced with meaningful values.