so far there was no place to track general issues related to the
Fedora CI infrastructure. We've created a new project to fix this:
If you run into any issue with Fedora CI testing and do not know
which exact tool is responsible for the problem, file issue here
and it will be routed to the right project/people.
Also if you have any ideas for improving the CI workflow feel free
and welcome to share them here. The old AtomicCI queue  will be
reviewed and general issues from there will be moved here.
as part of bringing upstream and downstream workflows related to
testing one more step closer together and allow easier automation
tools development and sharing between Fedora, Red Hat Enterprise
Linux and other products, the CI team is proposing to use a
consistent format for the CI related messages:
The specification (currently describing koji-build and brew-build
messages) is written in self-documented YAML files defining a
JSON SCHEMA which can be used to validate the message format.
Included is also a set of example messages to get a quick start.
Please, review the proposed format and share your feedback.
Here's something that Matt Miller did a drive by comment at Flock about
... and I wanted to relay the conversation to the people who can
actually help :)
Matt tried to work through the Fedora CI wiki  and get started with
tests, wrapping them, and placing in dist-git. He got through that ...
but then found no description of where he would see CI feedback in
Fedora, the form it would take ... how gating would work ... how waiving
I imagine part of this is because CI feedback has been disabled since
April. But this is just a heads up about the apparent gap in