On Wed, Mar 03, 2021 at 07:27:46PM +0000, Jeremy Stanley wrote:
Yeah, I don't see that being much different from hitting download.cirros-cloud.net during out image builds. If you're forking or otherwise making unofficial builds of Cirros though, you might want to name the files something which makes that clear so people seeing it in job build logs know it's not an official Cirros provided version.
I'd personally prefer to build it in a job and publish it so that you can see what's been done. Feels like a similar situation to the RPMs we build for openafs (see ~[1]). If you put your patch somewhere, you can use a file-matcher to just rebuild/upload when something changes. I see the argument that one binary blob from upstream is about as trustworthy as any other, though. -i [1] https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/playbook...