fedora-qa / fedora_openqa

#23 Drop the 'last tested compose' JSON stuff?
Closed: Fixed Opened by adamwill.

Closed: Fixed
Reopen Issue

So assuming D557 gets merged, I think it might be feasible to drop the JSON file that tracks the 'last tested compose' for current mode. I believe the force stuff provides the same protection. It'll mean the subcommand wakes up and jumps through a few of the same hoops every hour - checking the current event, looking for ISOs, realizing it already has them, and calling jobs_from_fedfind() - but it's not really a huge hit, it'll produce a few fedfind calls (i.e. HTTP requests to alt.fp.o) and a few openQA API hits every hour and that's about it. We could probably reduce it to the openQA API hits if we re-order how the force stuff is implemented a bit, even.

Note that the force stuff is effectively per-arch because it's per-ISO.

This ticket had assigned some Differential requests:
D557

The other way to reduce wasted work here is to write a fedmsg listener to trigger current instead of having it run every hour: it'd just have to listen out for changes to the CurrentFedoraCompose wiki page and call current whenever one happened.

Guessing the proper project, adjust if appropriate.

This was resolved long ago, we haven't had the JSON stuff in a while and we do have fedmsg scheduling.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/fedora_openqa/issues/23

Please continue any further discussion there.
Metadata
None
None
None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.