Open dougsland opened 4 months ago
Adding some folks in CC from automation, QE, Fedora/CentOS maintainers that might have some ideas about resources too.
cc @pbrilla-rh @juanje @Yarboa @pypingou @mwperina @sandrobonazzola
I would close this as won't do. I think that the resource consumption for doing this rather than dnf update <url to qm rpm build including the patch>
after a patch is merged on an existing nightly qcow image is not worth it IMHO.
Also, if you really need to have the image patched before running the VM you can possibly still do that with guestfish
by running the dnf update
on the image.
Let met start saying I am not sure if we have the resources to accomplish that via github or gitlab but let me add the scenario and requirements.
Imagine the scenario of new patch arriving to the project, CI/CD pipeline is triggered and it PASSED in all tests, the next step (which is about this issue) is generate a QCOW2 image with the new patch INCLUDED in the QM RPM available for download so developers and quality engineers can easily download and test it.
Example:
Finally, I am sure, this is not something exclusive for QM project, probably all components for centOS auto, like BlueChi could take adv. of such strategy and integration.
See-Also: How to build QM RPM / CentOS Auto:
https://github.com/containers/qm/tree/main/docs/devel#building-qm-rpm-manually-with-changes