Generate reports for OEM and base sysext images, allow reports against last nightly #1169
Commits on Nov 21, 2023
-
ci-automation/image-changes, .github/ci: Drop work directory parameter
It was only needed for the show-changes script. Now that show-changes script allows to set the repos parent directory with an environment variable, we set the variable instead of changing the working directory.
-
ci-automation/image-changes: Set NEW_VERSION in toplevel function
This avoid assuming that the current working directory in the generate_image_changes_report function is actually toplevel directory of the scripts repo.
-
-
ci-automation/image-changes: Strip kernel versions in initrd reports
This is something that we already do for production image and for OEM sysext images.
-
-
ci-automation/image-changes: Do not expect HEAD commit to have a tag
It certainly does happen on GitHub Actions that the HEAD commit has no tag. In such case, fake the tag from version file. The git tag in this scenario is used to figure out a channel transition.
-
-
.github/ci: Run image reports job after vms job
It shows changes also in OEM images and these are built in vms step.
-
overlay coreos-base/common-oem-files: Add some arch info about OEM
For now we don't have a single place where we could learn about which OEMs with a sysext image gets built for certain architecture. So add it for now to the coreos-base/common-oem-files package. Missing architecture info for an OEM that gets built only in a certain arch is not going to be fatal for the image changes job - we will just get a report for this OEM with messages about failures to download some files.
-
ci-automation/image-changes: Filter out OEM IDs not built for an arch
This is to limit the amount of reports consisting purely of failures, because some files were missing. And those files will be missing, because an OEM might not even have any image for certain arches (like digitalocean has no arm64 images).
-
-
ci-automation/image-changes: Source version.txt
This avoid messing with quotes.
-
ci-automation: List built base sysext explicitly
Instead of depending on default value of build_image's base_sysext parameter, create a file that explicitly lists which base sysexts will be built for each architecture. The file can be sourced by other scripts that need this kind of information. Currently, image.sh and image_changes.sh use this file.
-
overlay, ci-automation: Factor out OEMID info to a separate file
Image changes job needs a list of OEMIDs that are built for a specific architecture. Similar information already existed in the coreos-base/common-oem-files ebuild, so factor it out to a separate file, so the image changes job does not need to source the entire ebuild (or process it in other way), but rather source the smaller file.
-
overlay, ci-automation: Another attempt at providing OEMID info
Please read the comment at the top of the coreos-base/common-oem-files ebuild for details.
-
overlay coreos-base/common-oem-files: Move hack description down
EAPI needs to be defined within first 24 lines, so the description would push the definition too much down as it needs to happen after possible declaration of EAPI as local for the source case.
-
overlay, ci-automation: Try making common-oem-files a valid ebuild
Assignment of EAPI must be the first non-comment, non-blank line in the ebuild, otherwise portage masks it as corrupted.
-
-
-
-
.github/ci: Install python3-packaging package
show-fixed-kernel-cves.py script from flatcar-build-scripts requires this package: Traceback (most recent call last): File "/home/runner/actions-runner/_work/scripts/scripts/flatcar-build-scripts/show-fixed-kernel-cves.py", line 29, in <module> from packaging import version ModuleNotFoundError: No module named 'packaging' -
-
ci-automation/base-sysexts: Simplify
No need in making it arch-specific.
