autocloudreporter is a fedmsg consumer for reporting Autocloud results to ResultsDB. It listens out for Autocloud fedmsg messages, and submits results using the resultsdb_conventions module for conveniently reporting results in 'conventional' format.

The code was written with Python 3 in mind, but it turns out that verification of fedmsg message signatures does not currently work in Python 3, so it should be run under Python 2 for now.


Python libraries:


Install the required external Python libraries, then use setuptools to install, e.g.:

    python install

Test and production modes

Two consumers are provided, a 'test' and a 'production' consumer. For 'test':

  • The consumer listens for dev (not prod) messages
  • The consumer does not validate message signatures
  • The consumer reports to a ResultsDB instance running on localhost port 5001

In this mode it is safe to play around with the consumer, and you can use a tool like fedmsg-dg-replay to trigger event creation by replaying a relevant fedmsg (which will show up with a dev topic rather than prod).

For 'production':

  • The consumer listens for prod (not dev) messages
  • The consumer validates message signatures
  • The consumer reports to the production ResultsDB instance (if permitted)

PLEASE do not enable the production consumer on a system authorized to submit results to ResultsDB without checking with Fedora QA.

The fedmsg config keys for the consumers are autocloudreporter.test.enabled and respectively.


autocloudreporter is released under the GPL, version 3 or later. See COPYING and the header of itself.


Issues and pull requests can be filed in Pagure. Pull requests must be signed off (use the -s git argument). By signing off your pull request you are agreeing to the Developer's Certificate of Origin:

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.