search

coreos / fedora-coreos-cincinnati

Backend for Fedora CoreOS auto-updates (Cincinnati server)
Other
12 stars 16 forks source link

Hook up to Quay.io or OpenShift CI #9

Open jlebon opened 4 years ago

jlebon commented 4 years ago

I'd like to be able to write upgrade tests that require talking to a local dumnati server serving test-specific metadata. I'd much prefer just pulling down a container instead of rebuilding it locally as part of the test. :)

Easiest would be to hook it up to Quay.io or https://api.ci.openshift.org/. An alternative for users is pulling directly the image built in the Fedora OpenShift project, though offhand it doesn't look like the registry is exposed.

lucab commented 2 years ago

We are now using GH actions for ignition-validate, we can likely do the same here too: https://github.com/coreos/ignition/pull/1336

lucab commented 2 years ago

Just for clarity, the result of this would go into quay.io/coreos/fedora-coreos-cincinnati.