pá 10. 6. 2022 v 14:49 odesílatel Miloslav Trmac <mitr(a)redhat.com
pá 10. 6. 2022 v 2:02 odesílatel Do Not Reply <nobody(a)podman.io
Detected one or more Cirrus-CI cron-triggered jobs have failed
Cron build 'main' Failed:
Cron build 'release-1.4' Failed:
Cron build 'release-1.3' Failed:
These are real: k8s.gcr.io/coredns/coredns
got some Cosign signatures,
which are OCI artifacts, and c/image / Skopeo can’t currently copy
I suppose there’s no point in delaying adding OCI artifact support,
if only just enough for (skopeo sync) to work without having to
understand the signatures. I’ll start working on that now.
Gah! I made some progress on that in
(although I’m not quite
happy with it yet), but it turns out that our testing environment only
runs a very old registry that can’t accept OCI artifacts.
I think that’s
, isn’t it?
At this point I think insisting on just fixing the failure on the main
branch becomes impractical. Let’s use some other repo for testing, like
on the old branches, and then we can:
* Update the registry used for CI
* Take the necessary time to handle OCI artifacts and compression
* Split the OCI artifact work into smaller PRs
* … defer actually finishing the OCI artifact support, because
something else will probably come up …
Yep. That image is built along side of all other VM images by opening a
PR in the automation_images repo, then specifying the resulting Image ID
(i.e. `c<blahblah>`) in skopeo (and c/image) `.cirrus.yml` file. Poke
me if you need help.
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.